Use Case: Create an XT activity for specific CRM IDs
In Launch: There's an existing Target Load and Fire rule. In that rule, there's an Add Params to Page Load Request action.
Name: mbox3rdpartyid
Value: (a variable that contains the CRM ID value, from a data element)
I believe this part works, it's how to pull this in Target that I need help with.
In Target>Profile Scripts, I made a profile script called id_mbox3rdpartyid with this code: return profile.get('mbox3rdpartyid');
Then in Audience Library, I made an audience called IDaudience, set up as this: Visitor Profile: user.id_mbox3rdpartyid equals (case sensitive) 0000000000
(The id I used is the real ID and not zeroes.)
I created the activity and set the audience to IDaudience. The experience is not being shown. This is set up on a password protected site. I made sure the user has the ID I entered in the audience.
I also tried making a second Audience set up as: Custom: mbox3rdpartyid Equals (case insensitive) 0000000000. This doesn't work either.
Please assist.
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @m_alcantara It seems like the initial steps correct however there is little correction in profile script.
Here I made a test example on Luma site.
I've created a data element called CRM ID and provides constant value only for test. in your case I hope you are getting the CRM ID from data layer.
Map this data element to target request - Add Params to Page Load Request action.
In Target>Profile Scripts, I made a profile script called thirdPartyid where I'm returning the mbox3rdPartyId value as mbox param. as we're passing this as mbox parameter
Then in audience library made an audience called test ID like below
and then create the activity and assign the audience test ID and set the right traffic and setup m goals and setting
so here I'm able to get the below experience only for the test ID audience and I can able to see the mbox3rdpartyId in network call which I passed in through data element.
and here is the default version https://luma.enablementadobe.com/content/luma/us/en.html
Hope this helps.
Thanks.
Hi @m_alcantara It seems like the initial steps correct however there is little correction in profile script.
Here I made a test example on Luma site.
I've created a data element called CRM ID and provides constant value only for test. in your case I hope you are getting the CRM ID from data layer.
Map this data element to target request - Add Params to Page Load Request action.
In Target>Profile Scripts, I made a profile script called thirdPartyid where I'm returning the mbox3rdPartyId value as mbox param. as we're passing this as mbox parameter
Then in audience library made an audience called test ID like below
and then create the activity and assign the audience test ID and set the right traffic and setup m goals and setting
so here I'm able to get the below experience only for the test ID audience and I can able to see the mbox3rdpartyId in network call which I passed in through data element.
and here is the default version https://luma.enablementadobe.com/content/luma/us/en.html
Hope this helps.
Thanks.
@Gokul_Agiwal, thank you.
I checked the setup and did as you advised.
This is the Add params in Launch. Note that this isn't new. It's been set up for a while.
The data element used to set the value in this Add params is also used to set eVar12. I can see IDs populating in eVar12 in Analytics so the data element works fine. It's being pulled into Analytics.
After I checked the setup to match with your suggestion, I logged in to test but the activity. I did not see the modification. I checked in the Chrome dev console and it appears I did not qualify for the activity. Something is up with the ID.
I changed the Audience. Instead of:
Visitor Profile: user.ID_mbox3rdpartyid equals (case sensitive) 0000000000
I made it:
Visitor Profile: user.ID_mbox3rdpartyid Parameter is present
I did this to troubleshoot, so I can observe what's happening.
After changing the Audience to parameter is present, I logged in and I did quality for the activity and saw the modifications. I checked the dev console and noticed that the ID_mbox3rdpartyid is set to blank.
It looks like the ID_mbox3rdpartyid is not being set properly. However, as I mentioned, the data element I use to populate it in Launch is also used in an eVar and that eVar is being set correctly so I don't think the data element itself is not the issue.
As for the Profile Script, I did as you suggested, like this: return mbox.param('mbox3rdpartyid');
Views
Replies
Total Likes
@m_alcantara good that you made a change in profile script. regarding the ID is not getting set at Target level and coming as blank, it might be some timing issues and in your case the CRM ID is not getting set there. You can check the rule ordering in Launch, print your CRM id in console or through debugger you can check.
I did check and in my example it did set out correctly and I can able to see via response tokens.
Feel free to post further questions if any.
Thanks
Views
Replies
Total Likes
Views
Likes
Replies