SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site, support.twilio.com, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to help.twilio.com, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

Audience Sync Delays to Marketo Static List Destination

Issue

When syncing a Segment Engage audience to a Marketo static list destination, users may experience delays before audience members appear in Marketo. Sometimes, audience members are pushed immediately, while in other cases, there can be a delay of several hours.

 

Product

Segment 

 

Environment

Segment Console

 

Cause

Delays can occur due to several factors:

  • Multiple audiences syncing to the same destination share throughput, which can introduce delays.
  • Many destinations, including Marketo, enforce strict rate limits. Segment Engage automatically caps the number of requests per second to avoid triggering rate limits that could cause data to be dropped. For Marketo Static Lists, the cap is 5 requests per second.
  • Audience size, complexity, system load, and destination health can also impact delivery speed.
  • After initial setup, it can take six or more hours for an audience to start appearing in Marketo, especially for new or large audiences.

 

Resolution

  • Wait at least six hours after initial setup for audience members to appear in Marketo.
  • Use the Delivery Overview in Segment Console to monitor the status of audience syncs, including pending, failed, or successful deliveries.
  • Backlogs are cleared automatically by the system. If events remain stuck for several hours or show a failed status, further investigation may be required.
Have more questions? Submit a request
Powered by Zendesk