random duplicate profiles appearing in custom destination connector

[MarcSt5]

hi, I've recently developed a custom destination conenctor for streaming audience that pushes audience membership to Eloqua. The connector is set for testing purpose with a maximum time of 10 minutes or 10 profiles. Its all working perfectly, except I find quite randomly that the same profile with the same audience qualified date/time is pushed around 2 hours later again to the endpoint.

Would anyone have any idea why this would happen? I could expect that to happen if the profile qualified for the audience again 2 hours later, but it has the original qualified date and tme which makes no sense

thanks

Marc

[Devyendar]

@MarcSt5 here are few scenarios when profiles get updated on Audiences, and each update could trigger the destinationSDK flow, especially if it is a streaming segment.

• New profile data ingested (record or time-series) that meets/violates the audience rule → streaming eval fires.

• Late-arriving data lands that changes rule truth → re-evaluation/export.

• Identity graph changes / stitching (new identity links) alter which data is in the merge → membership can change.

• Merge policy changes (e.g., switching Active-on-Edge merge policy) → profiles may re-compute and audience membership can change.

• Segment definition change (rule edit, dependencies, “audience-of-audience”) → triggers re-evaluation.

Also check segment status transitions per profile (realized → exited → realized). Any change will emit an update and run the destinationSDK flows.

[Sukrity_Wadhwa]

Hi @MarcSt5,

Was the given solution helpful to resolve your query or do you still need more help here? Do let us know. In case the given solution was helpful, then kindly choose it as the 'Correct Reply'.

Thanks!

[marc_stowe_za]

Hi, the information was true but not really relevant to what is going on. The profile enters the audience and on odd occassions is sent twice, 2 hours apart. The status date is included, so i can see its exactly the same record, it hasnt left abnd re-entered the audience. It almost feels like the audience forgot that it sent it the first time and just sends it again to be sure