Pausing Audience Update to Destination | Community
Skip to main content
B
BenjaminPu
July 3, 2025
Question

Pausing Audience Update to Destination

  • July 3, 2025
  • 2 replies
  • 529 views

Hi, 

 

I have many audiences activated to destinations such as Facebook, The Trade Desk and Adobe Target. Circumstances may require these audiences to be edited to reflect updating targeting or suppression rules.

 

Is there a function within AEP (or workaround) that allows for pausing the segment refresh to the destination? For example, Trade Desk keeps the most recent set of profiles (Audience still is activated to the destination hence why it would still appear), but AEP does not send new profiles until the segmenting rules have been updated, and the audience activation has been 'un-paused'. 

 

Thanks!

    2 replies

    KumarRishii
    KumarRishii
    Level 5
    July 3, 2025

    To pause or control the audience refresh from AEP to destinations like The Trade Desk or Adobe Target:

    Deactivate the Segment: Temporarily deactivate the segment in AEP to stop the flow of new profiles to the destination while keeping the audience activated. The audience will still appear in the destination with the most recent set of profiles.

    Adjust Activation Conditions: Control the frequency of segment refreshes by modifying the refresh schedule (e.g., daily, weekly) to prevent premature updates.

    Use Suppression Segments: Create suppression segments to exclude profiles temporarily, which prevents the update of profiles without deactivating the entire segment.

    API-Based Control: Use Adobe I/O APIs to programmatically pause or resume audience updates based on specific conditions, though this requires development work.

    Destination-Specific Controls: Check if destinations like The Trade Desk or Adobe Target offer native controls for pausing updates directly within their platforms.

    Referral Link: https://experienceleague.adobe.com/en/docs/experience-platform/destinations/ui/edit-activation

    These workarounds allow you to control when and how new profiles are sent to your destinations while keeping audiences activated.

      Michael_Soprano
      Michael_Soprano
      Level 10
      July 5, 2025

      AI generated response for that user for xx time in this week. Something like this do not even exist....

       

      Use Suppression Segments: Create suppression segments to exclude profiles temporarily, which prevents the update of profiles without deactivating the entire segment.

        Sukrity_Wadhwa
        Community Manager
        Sukrity_WadhwaCommunity Manager
        Community Manager
        July 29, 2025

        @michael_soprano Thank you so much for flagging this and bringing it to our attention. We'll make sure it's addressed appropriately.

        Please keep the feedback coming. It really helps us keep the community experience clean and valuable for everyone.

        Sukrity Wadhwa
        B
        BenjaminPuAuthor
        July 15, 2025

        Hi @kumarrishii @michael_soprano , 

        Regarding deactivating the segment (option 1), adobe support has advised:


        One option is to temporarily disable the destination dataflows while you re-ingest the right data in AEP. See https://experienceleague.adobe.com/en/docs/experience-platform/destinations/ui/edit-activation#enable-disable-dataflows Pausing an activation dataflow halts updates; it does not remove or unmap previously exported profiles. This would allow you to run your campaigns while rebuilding your data in AEP, based on the last existing export to destinations before disabling the dataflows. When paused, no fresh profile activations or removals are sent, but the profiles at your downstream destination remain as-is until you resume. This means no risk of mass audience removal at the destination—you maintain the “last known state” until you re-enable the export.

        Was that what you were referring to? We trying to ensure that the connection to the destination is not being interfered with when enable/disabling the dataflow. 

         

        Thanks!

        Terms & ConditionsAccessibility statement

        Loading footer...