Expand my Community achievements bar.

Join us on September 25th for a must-attend webinar featuring Adobe Experience Maker winner Anish Raul. Discover how leading enterprises are adopting AI into their workflows securely, responsibly, and at scale.
SOLVED

Access parameters and IDs from RT-CDP via Websdk and mobile sdk

Avatar

Level 2

Hi everyone, 

 

In my current adobe setup, I have AEP, Event forwarding and Adobe data collection. The use case I have requires me to send data from Websdk to Event forwarding property to Google Analytics. For this particular use case, I need to generate new google client if it doesnt exist and use the existing google client ID if it does exist. How can I do so? Is there a way for me to refer to IDs/parameters stored in AEP using rules or data element in Data collection/launch? If this can be achieved, is this near real time? What is the delay here? 

 

TLDR; Refer to data stored in AEP using adobe launch/data collection. 

 

Thanks for helping :))

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

There is currently no way to access profile information in server-side forwarding. I once heard that Adobe might introduce this at some point, but currently server-side only has access to the raw event data.

So, if you need to access any kind of user identifiers, they have to come with the event payload.

 

Using the AEP APIs could be quite cumbersome, so my recommendation would be the above mentioned approach.

Cheers from Switzerland!


View solution in original post

3 Replies

Avatar

Community Advisor

Hi @Aakash_13 

it should be explained here: https://experienceleague.adobe.com/en/docs/experience-platform/tags/event-forwarding/overview

 

IMG_2264.jpeg

 So, for your Google ID you should make sure to put the logic in launch client-side and throw it into the request payload. In this case, I would suggest using the freeform "data" section which does not require a predefined XDM schema e.g. data.google.id or whatever makes sense to you.

This you can then reference in Launch server-side data elements with arc.event.data.google.id

 

As mentioned, I would keep the logic on launch client-side since it is a lot easier to debug.

Cheers from Switzerland!


Avatar

Level 2

Hi @bjoern__koth , 

 

Thanks for the reply. 

 

Maybe I didnt explain the scenario properly but I am not talking about referencing the variable in Event forwarding property from client side.

 

Consider this scenario:

 

A new user gets on the website and they get assigned a GoogleID. I can reference this ID server-side and send with the payload to Google Analytics however, if the same user gets on the website again I need to check if its a new user or an existing user and for that the only way (I can think of) is to compare it existing google ids. Assuming I have these stored in AEP. Is there a way I can compare the google id with stored google ids in AEP and decide if I have to generate a new google id or not. 

 

Hope this clears things up. 

 

Thanks

Avatar

Correct answer by
Community Advisor

There is currently no way to access profile information in server-side forwarding. I once heard that Adobe might introduce this at some point, but currently server-side only has access to the raw event data.

So, if you need to access any kind of user identifiers, they have to come with the event payload.

 

Using the AEP APIs could be quite cumbersome, so my recommendation would be the above mentioned approach.

Cheers from Switzerland!