Google Ads: current access and control boundary

Google Ads can connect an agency's advertising account, but it is not yet a public self-service journey for creating, importing, synchronizing, enabling, or pausing campaigns. Those actions can change an external account and commit real spend.

Until Holidario confirms in writing that campaign controls are ready for your account, use this integration only to prepare assisted implementation and review information without executing changes.

Responsibilities and access#

• Holidario maintains the application's technical credentials and coordinates initial activation.
• Your agency identifies the correct account, designates who may authorize it, and retains control of campaigns and billing.
• The advertising account, balance, policies, users, and costs remain your agency's responsibility.
• Seeing an integration or campaign does not grant authority to synchronize, import, enable, pause, or change budget.

The Agency plan includes the feature, but that does not grant access to every team member.

Prepare assisted implementation#

You need:

• an active Google Ads account and the Google user who can authorize it;
• the customer ID in 000-000-0000 format;
• its MCC ID if a manager account is used;
• a reviewed booking site and destinations;
• a person authorized to approve budget and publication;
• a test window and an explicit condition for stopping any change.

Do not send credentials, OAuth codes, developer tokens, or payment data by email or ticket. If the screen reports missing application credentials, request assistance; those credentials belong to the platform.

What your team may review#

With read access, you may check:

• that you are in the correct team;
• which advertising account is intended for connection;
• the name, commercial state, budget, and synchronization state shown for a local campaign;
• who is responsible for approving any change;
• the real publication, spend, and billing state directly in Google Ads.

A Connected label confirms a local integration state. It does not by itself prove that the account, permissions, billing, campaigns, or measurement are ready.

Actions outside the public journey#

Do not use the following as self-service:

• Import Campaigns from Google Ads;
• Sync to Google Ads;
• creating or editing a campaign intended for synchronization;
• enabling or pausing campaigns individually or in bulk;
• disconnecting and reauthorizing to try to repair an error;
• repeating an action whose result is uncertain.

These actions need accepted permission and resource controls, a known test account, and a person accountable for spend. A visible button does not mean that the journey is accepted for your organization.

Request activation#

Email [email protected] with:

• team name;
• partially masked customer ID and MCC where applicable;
• the Google account and user who will authorize, without credentials;
• proposed test campaign and maximum budget;
• destination pages and measurement to review;
• the person approving the change and the person checking the result in Google;
• execution window and stop condition.

Holidario must confirm the exact scope before OAuth begins or a campaign is touched. Acceptance of a connection does not automatically authorize later imports, synchronizations, or spend changes.

If a connection already exists#

Keep Google Ads as the verification source for publication, budget, billing, and users. If Holidario and Google show different states:

• do not repeat synchronization;
• do not duplicate the campaign;
• record account, campaign, time, local state, and external state;
• contain spend in Google Ads if your accountable owner considers it at risk;
• escalate the discrepancy for assisted review.

Do not disconnect as a test: removing local authorization does not pause or delete campaigns active in Google.

Expected result#

The agency knows the correct account and accountable owner, can review state without confusing it with real spend, and executes no external action until the journey is explicitly accepted.