Handling Demandbase and Adobe Target Timing Conflicts on First Page Load (with GDPR & Consent Considerations)
Hi everyone,I wanted to start a discussion around a challenge we’re running into with Adobe Target and Demandbase integration — particularly the timing conflict on the first page load, and how it impacts personalization.Our current setup:Adobe Target is implemented via Adobe Launch, loading synchronously (no flicker snippet used).Demandbase is also implemented via Launch using the OOTB extension.Both Target and Demandbase are triggered on the "Page Top" rule.We are also GDPR-compliant, and use TrustArc’s OOTB extension within Launch to manage cookie consent. So any personalization or tracking solution must respect the user’s consent state.The challenge:Because Target executes immediately on load, its call typically fires before Demandbase returns any firmographic data, making it impossible to personalize on a visitor’s first page hit. This severely limits our ability to deliver relevant content based on company-level attributes (industry, size, etc.).We’ve explored a few directions:Ser
