Forum Discussion

andrewdonnelly's avatar
andrewdonnelly
Active Member
2 years ago

How to record the origin of all users in Braze - Best practices

I'm looking to hear from someone who records the origin of all their Braze users and how best to do this. Do you use a custom attribute? If not, what do you use? Or do you record it outside of Braze?...
Reporting and Analytics
andrewdonnelly's avatar
andrewdonnelly
Active Member

Thanks for your reply Max. We're not using either AppsFlyer or Adjust. But I'll look into both. 

Native attribute in the user profile - that kind of answers my question. It would be interesting to see how the data is structured in such an attribute. I tried googling this but can't find any examples. Do you use a native attribute or custom attribute to store the user's source? Is it a nested attribute or an array of objects?

Thanks

Max's avatar
Max
Specialist
2 years ago

Hey andrewdonnelly, regarding your answers:

Firstly, as AllanHeo  mentioned, I'm not talking about custom attribution. Braze has the ability to sync install attribution through direct integration from app attribution partners like Adjust or AppsFlyer. This would look like this in the engagement tab of the Braze user's profile:

This is a native and direct integration in the user profile, similar to device and profile information.

You can use the install attribution data in your campaign or canvas entry filter. For example: You want to send a communication (like a voucher code) to every customer that comes from TikTok. No problem. The data will be synchronized between your install attribution software (through SDK or API) along with the ad group etc.

Check out the Braze documentation for more information and how it works:

You also can use the Braze query builder to check how many customers are coming from which sources in which week. Something I like to do pretty often:

 

SELECT 
    SOURCE,
    EXTRACT(WEEK FROM SF_CREATED_AT::timestamp) AS week_number,
    COUNT(*) AS users_count
FROM USERS_BEHAVIORS_INSTALLATTRIBUTION_SHARED
GROUP BY SOURCE, week_number
ORDER BY week_number DESC;

Let me know if you need any further information or help 🙂 .

Best,

Max