Personalization Can Become a Throughput Problem
Journey injection looks healthy, but email build/send throughput falls behind and queue depth grows.
Trust & provenancePRODUCTION
Evidence tierPRODUCTIONOfficial sources2Other sources0Last verifiedNot recorded
Evidence tier describes my hands-on relationship with the content. Official sources describe platform contracts/documentation. Production observations should not automatically be treated as official limits.
Heavy per-recipient work such as repeated LookupRows() or remote HTTP calls increases message build cost. Salesforce specifically points to excessive LookupRows()/HTTPGet() as a queue-backlog troubleshooting path.
What to check
- Count lookups/remote calls performed per recipient.
- Check whether repeated data can be staged before send.
- Compare injection speed with email build throughput.
Make it cheaper next time
- Precompute expensive segmentation/personalization where possible.
- Keep email-time logic small, bounded and defensive.
ampscriptjourneyperformancelookuprows