sending measurement results via AEP API vs Event Forwarding | Community
Skip to main content
C
crispypop
Level 2
October 30, 2023
Solved

sending measurement results via AEP API vs Event Forwarding

  • October 30, 2023
  • 1 reply
  • 1745 views

Hello 

 

Has anyone considered using AEP APIs to collect profile data (e.g. hashed email/phone, etc) and sending via using APIs vs configuring EventForwarding using the dataloader???

 

I'm thinking this saves the time of the application to find and source customer info that the application won't have... but the AEP profile will

 

thanks!

Best answer by Chasin

@crispypop If I'm following correctly, it looks like you need to forward event records that include other attributes like hashed email, phone, etc. to the Meta Conversions API.  If you're using Advanced Matching, or if you set the client-side Meta Pixel to auto-send form data, you may already be sending some of that data via the pixel.

 

Option 1: for authenticated visitors, read the source data (email, etc), send it in a sendEvent call from Web SDK, then send to Meta in Event Forwarding with the cAPI extension.

Option 2: collect event IDs and all required event attributes as they occur client-side (using your systems to collect & store), combine them with the other data you have & want to send to Meta, then use the Edge Network Server API to stream or batch send those event records (with all needed data) to Adobe, then use EF + Meta cAPI extension to stream them to the API.

Option 3: if you know you have the attributes you need stored in a Platform dataset, and you have a unique identifier you can use as the key to query for those attributes, you might be able to query a Platform API to retrieve those attributes, then combine them with your event record data, and send to Edge Network Server API as above. Querying Platform APIs from Event Forwarding for this use case is not currently available or supported, so in concept that would be done from your systems, then send to Edge API, etc.

 

Many customers simply work with their front end team(s) to make the additional attributes available in the browser and the events, and go from there.

1 reply

Anil_Umachigi
Adobe Employee
Anil_UmachigiAdobe Employee
Adobe Employee
October 31, 2023

@crispypop AEP API for profile and event forwarding serve two different pupose and do not have same level of data. 

Profile data is consolidated information of events and records while event forwarding is a "single event" which is transmitted as it happens. 

 

Could you expand on usecase? 

 

Anil

C
crispypopAuthor
Level 2
October 31, 2023

Hi Anil

 

thanks for response

 

The use case is... we have marketing publishers who want more accurate measurement, so they are wanting integrations like Facebook Conversion API.  I know AEP offers this specific integration within Event Forwarding.  The issue is that publishers want more customer info (e.g. hashed email, phone) as part of the event.  Most events don't have that... but profile store does.  It's also not critical that we send that info in real time (once of day is fine).  So, i'm wondering if there's way to use AEP/RTCDP to send profile fragments to the likes of Facebook CAPI

 

thanks!

Chasin
Adobe Employee
ChasinAdobe EmployeeAccepted solution
Adobe Employee
October 31, 2023

@crispypop If I'm following correctly, it looks like you need to forward event records that include other attributes like hashed email, phone, etc. to the Meta Conversions API.  If you're using Advanced Matching, or if you set the client-side Meta Pixel to auto-send form data, you may already be sending some of that data via the pixel.

 

Option 1: for authenticated visitors, read the source data (email, etc), send it in a sendEvent call from Web SDK, then send to Meta in Event Forwarding with the cAPI extension.

Option 2: collect event IDs and all required event attributes as they occur client-side (using your systems to collect & store), combine them with the other data you have & want to send to Meta, then use the Edge Network Server API to stream or batch send those event records (with all needed data) to Adobe, then use EF + Meta cAPI extension to stream them to the API.

Option 3: if you know you have the attributes you need stored in a Platform dataset, and you have a unique identifier you can use as the key to query for those attributes, you might be able to query a Platform API to retrieve those attributes, then combine them with your event record data, and send to Edge Network Server API as above. Querying Platform APIs from Event Forwarding for this use case is not currently available or supported, so in concept that would be done from your systems, then send to Edge API, etc.

 

Many customers simply work with their front end team(s) to make the additional attributes available in the browser and the events, and go from there.

    Terms & ConditionsAccessibility statement

    Loading footer...