Nível 1
Nível 2
Faça login na Comunidade
Faça logon para exibir todas as medalhas
Hi,
Event forwarding data elements utilizes XDM object as data source and Edge network forward those data elements values to non-adobe solutions. My question is in case of non-xdm data, what could be the data source for event forwarding data elements? Any document or example on sending non-xdm data would be helpful.
Solucionado! Ir para a Solução.
Visualizações
respostas
Total de curtidas
Here are some samples to create data elements:
based on the guideline given here https://docs.mktossl.com/docs/experience-platform/tags/event-forwarding/overview.html?lang=en#data-e...
The make fetch call looks like this:
See if this helps.
Visualizações
respostas
Total de curtidas
@vikash4 are you able to pass the non-xdm data to the data collection?
The data that comes to the data collection with XDM object, you can remap by adding rules & data elements and pass it in the format that you like to the non-adobe extension.
Visualizações
respostas
Total de curtidas
@ChetanyaJain I am passing XDM data into data collection and using Event forwarding property to send it to non-adobe solution. I'm using Adobe Cloud Connector extension with "Make Fetch Call' action type in Event Forwarding property. XDM compliant data is flowing to non-adobe solution.
In order to send non-xdm data to non-adobe solution, how to do remapping? Any document or example around this would be more helpful.
Visualizações
respostas
Total de curtidas
Here are some samples to create data elements:
based on the guideline given here https://docs.mktossl.com/docs/experience-platform/tags/event-forwarding/overview.html?lang=en#data-e...
The make fetch call looks like this:
See if this helps.
Visualizações
respostas
Total de curtidas
@ChetanyaJain Thanks for your efforts
I think I'm doing the same steps for sending data to non-adobe solutions from XDM data collection.
In event forwarding data element I'm referring XDM data
elements(arc.event.xdm.identityMap.pmiCrmId.0.id & arc.event.xdm.identityMap.ECID.0.id) and in rule mapping them to send as query parameter.
My question is, instead of referring the xdm data element, can we map non-xdm data element with event forwarding data element like instead of using arc.event.xdm.identityMap.pmiCrmId.0.id & arc.event.xdm.identityMap.ECID.0.id, can I use arc.event.person.name.firstName & arc.event.person.name.lastName considering firstName & lastName is not part of XDM data element?
Visualizações
respostas
Total de curtidas
@vikash4 I am wondering how will you populate the data element if it's not part of the data layer that gets ingested from websdk/mobilesdk/server API?
To ingest the data into data collection, you will need the xdm defined and then you will forward it to non-adobe.
Please let me know if I am missing or overlooking the fundamentals.
Visualizações
respostas
Total de curtidas
@ChetanyaJain I don't know about this use case so thought to check if anyone has implemented or I can get any document or example around this.
Visualizações
respostas
Total de curtidas
Also, there are other data element types other than Path - not sure if you have tried that.
Visualizações
respostas
Total de curtidas
@vikash4 ,
You can access the custom objects as well with in event forwarding.
As an example I am referring the custom value that I send through data filed section to server side and I refer the value on the event forwarding like below.
arc.event.data.facebook.fbp
If you want to understand how the arc object look like to get to understand the exact path of your field - write your complete object an end point. I use webhook for this
Visualizações
respostas
Total de curtidas
Visualizações
Curtida
respostas
Visualizações
Curtida
respostas
Visualizações
Curtida
respostas