AdSync account permissions and launch control

Review what you authorize

The published AdSync workflow uses Google authorization for CM360, Google Ads and GA4, and Meta authorization for Meta Ads. Your provider account’s role and the permissions granted to the application both affect what it can do.

Connect only the accounts needed for the workflow. During onboarding, confirm the account identifiers and the operations your team intends to permit. Do not share account passwords through the website contact form.

Separate validation from publication

AdSync starts in read-only validation mode so you can review campaign data and proposed changes before anything is written. Publishing is an explicit action controlled by your team.

Use a controlled campaign during the first walkthrough. Review the proposed scope and platform response, then check the live records before using the same process more broadly.

Questions to resolve before connecting production accounts

• Which permissions and account roles are needed for our exact operations?
• Who can authorize connections and approve a live push?
• Where are campaign data and authorization tokens stored, and for how long?
• How do we revoke access and request deletion or export?
• What audit records and support procedures are available?
• Which security reviews, contractual terms and data-location requirements can be documented?

Website inquiries and application data

The website contact form collects the information you submit to handle your inquiry and uses a security challenge to reduce automated abuse. Its privacy policy describes this website’s handling of inquiry data.

Application campaign data has a different scope from a website inquiry. Request the applicable application terms and a walkthrough of the current data handling before onboarding. No certification or independent security audit is claimed on this page.