AEP Data Distiller audience expires despite scheduled overwrites

A Data Distiller query can refresh audience rows every day while the audience itself approaches its expiration date. An Experience League practitioner reported that the profile count dropped at expiry despite scheduled overwrites. After testing, the poster said Adobe’s external-audience TTL endpoint extended the audience successfully. The operational trap is treating a data refresh and a retention refresh as one event.

Check the clock on the audience

Record the audience ID, sandbox, last successful ingestion, expiration time, and activation destinations. Adobe’s Data Distiller audience guide describes a 30-day retention period for SQL-created external audiences. Compare that rule with the actual expiry displayed in Audience Portal; do not infer a fresh expiry from a successful scheduled query alone. Add an alert before the expiry window closes so a zero profile count is not your first signal.

Extend the right object

Adobe documents POST /ais/external-audience/extend-ttl/{AUDIENCE_ID} for external audiences. Its guide says the extension uses the original duration, or 30 days when none was set, and re-ingests data from the last successful ingestion. The community author says this endpoint also worked for their Data Distiller-created audience. Test it in the relevant sandbox with the actual audience ID, then read the response and audience state back. Re-run the scheduled query only if the resulting membership or ingestion timestamp is not what activation needs.

Make expiry part of the runbook

Assign an owner to the audience lifecycle, not just the SQL job. Keep the audience ID, extension result, expiry date, and destination readiness in one operating record. Verify a small sample of expected profiles at the destination after the extension. If the API rejects a SQL-created audience in your environment, preserve the request and response for Adobe Support instead of silently recreating a new audience with a different ID.

Adovo’s view

Fresh rows are not a live audience. A pipeline is complete only while the object that downstream teams depend on remains usable. Govern the audience’s expiration as a separate production clock, and verify the customer can still be reached after every refresh.