Solved

What is the best practice to track the source of profiles ?

  • 29 March 2022
  • 1 reply
  • 286 views

Badge +2
  • Contributor II
  • 3 replies

Hi,

What is the best practice to track the source of profiles ?

We understood that the $source variable was a "technical" variable whose value could be overwritten in the life of the profile.
e.g. :
1 - a profile is created with $source = Facebook Leadgen campaign
2 - the profile buys on Shopify. The $source becomes -50 for Shopify.
It becomes impossible to calculate a conversion rate by source...

So we created the Custom Property Source (without $) but we can't find it when we edit the profiles... also impossible to use the Custom Property "Source" to create a segment...

Any help?

icon

Best answer by alex.hong 31 March 2022, 07:22

View original

1 reply

Userlevel 7
Badge +58

Hi there @mdh,

Hope to help add some detail into what might be going on.

If you have created the custom property AND see that it is being logged under a user’s profile, then that leads to one possible error. However, my guess is that you are not seeing the custom property within a profile therefore we cannot segment from it. Adding a custom property doesn't automatically add this profile to the segment in question. In fact, due to the nature of how segments work, you simply cannot add profiles as you wish. The segment exists based on a set of pre-defined definitions or criteria. In this case, it's anybody who has come from your “source”. Unfortunately if the event source has not shown in this customer profile history they will not appear in the segment.  You can run a historical sync by going to your integration tab and click " re-import historic data" button to run any updates for your account. If the customer source value still does not show the only other alternative is to manually add the email to the segment. But we prefer and recommend for customers to be added to segments organically versus manually adding them to the segment. 

 

Once you confirm source is being loaded successfully as the custom property, then we can see what might be going on.

 

All the best,

Alex

Reply