Scope
Define audience types, pages where pixels are allowed, and campaign objectives in precise terms to prevent misuse.
A written retargeting agreement documents consent, clarifies responsibilities for pixels and data processing, reduces regulatory risk, and sets operational rules for campaigns. It helps ensure compliance with federal privacy norms and state laws, assigns liability for breaches or misuse, and defines audit and retention expectations for both marketing and legal teams.
Typical parties include marketing agencies, website publishers, adtech vendors, and in-house marketing teams who exchange tracking capabilities and audience signals.
Each party uses the agreement to set technical responsibilities, data handling rules, and consent obligations so that campaigns run with documented legal and operational guardrails.
The Marketing Director signs to authorize campaign scope and budget, confirms lawful consent mechanisms are in place, and accepts operational obligations such as pixel placement, reporting cadence, and campaign KPIs on behalf of the advertiser or brand.
The Website Owner signs to permit installation of tracking code, to confirm site-level disclosures and cookie banners, and to accept technical obligations for uptime, access control, and timely removal of tags when campaigns end or are disputed.
| Field | Configuration |
|---|---|
| Cookie Type | First-party cookie or server-side identifier |
| Consent Mode | Block until explicit user consent |
| Access Controls | Role-based accounts for tag changes |
| Audit Trail | Enable immutable logs for deployments |
Confirm supported formats, integrations, and authentication options before deployment.
Ensure the selected e-signature provider supports required integrations and file formats used across legal, ad ops, and analytics teams.
| Document Type | Primary Purpose | Enforceability |
|---|---|---|
| Retargeting Agreement | targeted ad consent | contractual |
| Data Processing Agreement | processor obligations | contractual |
| Privacy Policy | notice to users | statutory/notice |
| Cookie Consent Banner | consent mechanism | consumer consent record |
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day trial | Free trial | Free trial | Free trial | Free trial |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
Define audience types, pages where pixels are allowed, and campaign objectives in precise terms to prevent misuse.
List identifiers, behavioral signals, and any PII; specify allowed transformations and derived signals.
Require that publisher maintain notices and consent banners and document consent flows for audits.
Specify encryption, access controls, and breach notification timelines including responsibilities for investigations.
Identify permissible subprocessor categories and require written notice for new third-party recipients.
Define removal timelines for tags, post-termination data deletion, and indemnity for unlawful processing.
Obtain consent before firing third-party tags
15 days to remove tags after termination notice
Notify parties immediately; state laws vary on specific hours/days
30 days to cure material breaches
60 days advance renewal or nonrenewal notice
Finalize scope, retention, and opt-out language before sign-off.
Provision pixels and test consent gating during staging.
Begin audience build and report performance per schedule.
Evaluate compliance and renew or terminate per notice terms.
Optica adopted online agreements to streamline partner onboarding
A small publisher used mobile signing to approve tags onsite