Hello Community,
I am working on integrating 3rd party tool (tool allows to understand engaged users on our website) with Target for personalization. This integration is via Launch and maps Adobe variables in rules. Integration says you will be able to utilize these Adobe variables within Adobe Target to configure your A/B test or dynamic personalization.
However, I am unable to pull these variables for creating the audience. has anyone in the past been able to pull Adobe variables directly while creating variables?
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Dear @JyotiSharmaV ,
You should parse the Segment Details on the page and then grab it in the Target Parameter.
A few steps are fine, but it is not absolute now. Let's connect on the bridge and close it, then you can share the final output here for everyone's reference.
Thank You, Pratheep Arun Raj B (Arun) | NextRow Digital | Terryn Winter Analytics
Dear @JyotiSharmaV ,
Make sure that you are sending the variables to Adobe Target as MBOX Parameters or Profile Parameters. If yes, it should appear in the 'Custom' definition of the Audience Library.
For more help, you can share the public URL and the variable details here, we can validate the same for you.
Thank You, Pratheep Arun Raj B (Arun) | NextRow Digital | Terryn Winter Analytics
Thanks, @PratheepArunRaj We are almost new to Target. I found this doc https://experienceleague.adobe.com/docs/target-dev/developer/client-side/global-mbox/pass-parameters... but I am not sure where I need to code this.
Dear @JyotiSharmaV,
Hope you are already triggering Adobe Target Beacon from your website (By adding Adobe Target Extension and a rule to load & fire Adobe Target).
If yes, you need to add MBOX Parameters to the beacon (rule to load, add params to the requests & fire) and there are plenty of documents available on how to tag MBOX Parameters to the Adobe Target Beacon directly or using Adobe Launch. Kindly checkout.
Thank You, Pratheep Arun Raj B (Arun) | NextRow Digital | Terryn Winter Analytics
I did share that doc in my last message which says passing parameters to mbox call but as I am new to Target I don't see any step to step configuration to understand how to pass that. If possible can you share the dummy rule created by you to understand how to do that?
Hey @PratheepArunRaj , I read many docs, and looks like this is the correct way to what I want to achieve but my scenario has one additional step. I checked this doc, where it says Request Mbox, and if you see the "validate request parameter" part below shown there, it's exactly where i want to see my variable coming up in the below screenshot from adobe doc.
However, In my case, I have 3rd party tool, where I have my segments already build and I am pulling those segments in to launch to push them to Target in order to create an audience.
The segment field on the left(with a drop-down in screen-shot-1 below) is coming up from the integration that I have done with my 3rd part tool and on the right hand in screen-shot-1 "custom parameter" is the "Adobe Field or variable" to which I have to map my segment so that I can use that custom parameter (variable) in target for audience building ( screen-shot-2)
screen-shot-1)
screen-shot-2)
When it will be achived, then finally it should appear to me like below in dev console:
Hope I am able to reproduce the scenario for you to suggest.
Thanks
When doing action type Add Params to page Load Request it asks for mapping Value to Name of the parameter.
I dont have any data element to map in the above action type. I have my segment that is mapped in to my adobe variable
I tried following this doc to test Request Mbox param but unable to load any page load param in server call.
Do you know why this is happening? It shouldn't be a problem because it's a basic page load param mapping on target hits.
Dear @JyotiSharmaV ,
You should parse the Segment Details on the page and then grab it in the Target Parameter.
A few steps are fine, but it is not absolute now. Let's connect on the bridge and close it, then you can share the final output here for everyone's reference.
Thank You, Pratheep Arun Raj B (Arun) | NextRow Digital | Terryn Winter Analytics
Not sure if what do you men my Adobe variables
- Target: You have few options to send data part of the mBox parameters or profile parameters
- Adobe analytics: Share your segment to custom attribute and you will see the analytics segments
- Adobe Audience manager: shared segment will populate in drop down
Thank
Hey Community Advisors, Any suggestions on this thread? Thanks
Views
Like
Replies