Capturing Real-Time Events in Adobe Experience Platform | Community
Skip to main content
JeanBaro_
JeanBaro_
Level 4
July 29, 2024
Solved

Capturing Real-Time Events in Adobe Experience Platform

  • July 29, 2024
  • 1 reply
  • 2257 views

Hello,

I need to capture Adobe I/O Events for the following actions as quickly as possible:

  1. New Profile Creation: When a new Real-Time Customer profile is created.
  2. Profile Update: When an existing Real-Time Customer profile or any of its related objects (custom or native) are updated.
  3. Profile Merge: When two or more (Customer) profiles are merged into one.

These events need to trigger webhooks to sync downstream systems with AEP in NEAR real-time. Any tips on ensuring these events are fired promptly?

Thank you!

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by nnakirikanti

Hello,

Great news! We now have the ULTIMATE version, so HTTP Destination is back in play. This means we can publish profiles (creation or changes) in a streaming fashion to our PubSub, and then to Salesforce (that would consume those messages from PubSub).

We need to get those profiles out of AEP quickly, so ETL won't work for us.

Thank you so much for your time and help. I really appreciate it!


Excellent, Hope this solves your design. 

Please mark this thread accordingly .

 

~cheers,

Naresh Nakirikanti.

1 reply

nnakirikanti
Community Advisor
nnakirikantiCommunity Advisor
Community Advisor
July 30, 2024

Hello @jeanbaro_ given current platform capabilities there is no such I/O events for your use case, however given your licensing SKU's you can leverage alternative services to achieve few of this.

 

Streaming mechanism: If you have Ultimate package, you could use HTTP API destination, Amazon Kinesis, Azure Event Hubs to handle by creating streaming segment includes all the profiles and add mapping with Audit Attributes for updates

https://experienceleague.adobe.com/en/docs/experience-platform/destinations/how-destinations-work/profile-export-behavior#streaming-profile-destinations

 

Batch Mechanism: If you data distiller you can schedule a query based on some audit attributes from profile snapshot dataset to a derived dataset after daily global segment job and activate dataset to batch destination and process acordingly.

 

I hope this helps to some extent to solve your case, let me know if you more details.

 

~cheers,

Naresh Nakirikanti.

 

 

JeanBaro_
JeanBaro_Author
Level 4
July 30, 2024

Hi Naresh,

Thinking about the BATCH Mechanism (Custom Middleware?) you mentioned:

Would it be feasible and cost-effective to set up it in a way that:

  • Polls AEP via API every minute?
  • Returns only profiles created or updated since the last successful poll?
  • Identifies profile merges so we can inform other systems?

The middleware would publish these events to our Enterprise PubSub, which Salesforce subscribes to.

My concerns are:

  • Is it okay to poll AEP every minute? Is there any throttling on how many times we could call that AEP API?
  • Would this strategy incur additional costs?
  • Can we identify profile merges in the polled data?

The MERGE "event" needs to be created in that Middleware, and to be effective (in Salesforce) it would need relevant information about the MERGE profiles. 

Maybe this API could be used as a starting point? 


This is a pseudo-payload to try to better clarify the goal here:

 

{ "transactionId": "unique-transaction-id", "transactionTime": "2024-07-29T12:34:56.789Z", "eventType": "profileMerged", "winningProfileId": "winning-profile-id", "losingProfileIds": ["losing-profile-id-1", "losing-profile-id-2"], "mergeTimestamp": "2024-07-29T12:34:56.789Z", "mergeDetails": { "profilesMerged": 2, "source": "Identity Service", "additionalInfo": "Merged due to email match" } }

 

Thanks

 

nnakirikanti
Community Advisor
nnakirikantiCommunity AdvisorAccepted solution
Community Advisor
August 8, 2024

Hello,

Great news! We now have the ULTIMATE version, so HTTP Destination is back in play. This means we can publish profiles (creation or changes) in a streaming fashion to our PubSub, and then to Salesforce (that would consume those messages from PubSub).

We need to get those profiles out of AEP quickly, so ETL won't work for us.

Thank you so much for your time and help. I really appreciate it!


Excellent, Hope this solves your design. 

Please mark this thread accordingly .

 

~cheers,

Naresh Nakirikanti.

    Terms & ConditionsAccessibility statement

    Loading footer...