Google Integrations

Sophosic supports Google integrations that help operators measure traffic, attribute conversions, and manage reputation.

Available Google Integrations

Console Setup Preview

Before connecting Google services, confirm the operator is in the correct workspace and can see the intended integration card.

If the card is missing, disconnected, or attached to the wrong workspace, stop before copying provider IDs.

Consent First

Before enabling analytics or ads, review Privacy and Legal settings. Cookie consent and Global Privacy Control behavior affect whether tags can collect data.

Basic rules:

• Analytics should respect analytics consent.
• Ads should respect marketing consent.
• Global Privacy Control should suppress advertising signals.
• Advanced consent modes require explicit workspace acknowledgement.
• Booking tokens and other sensitive query parameters should not be sent to Google.

Google Analytics

Use Google Analytics when the workspace wants public site traffic measurement.

Setup:

1. Create or choose a GA4 property in Google.
2. Copy the Measurement ID.
3. Open Settings > Integrations > Google Analytics.
4. Paste the Measurement ID.
5. Enable the integration.
6. Verify the public site loads the tag after consent conditions are satisfied.

Expected ID format:

G-XXXXXXXXXX

What the operator should see:

Google Ads

Use Google Ads when the workspace needs conversion attribution for paid traffic.

Setup:

1. Copy the Conversion ID from Google Ads.
2. Optionally copy the conversion action label for explicit conversion events.
3. Open Settings > Integrations > Google Ads.
4. Paste the Conversion ID and label.
5. Choose consent mode.
6. Complete required legal acknowledgements.
7. Enable the integration.
8. Test a booking confirmation path.

Expected Conversion ID format:

AW-123456789

Conversion labels use letters, numbers, underscores, and hyphens.

What the operator should see:

Booking Conversion Tracking

Booking conversion events fire from booking confirmation pages when:

• Google Ads is enabled.
• The Conversion ID is valid.
• A conversion label is present for explicit event tracking.
• Consent conditions allow the event.
• The event has not already fired in the browser session.

The event should use the booking ID for dedupe and should avoid sending booking access tokens in page location.

Verification Preview

Use this sequence when diagnosing Google measurement or attribution:

Google Business Profile

Use Google Business Profile when the workspace wants reviews and business listing data connected to the console.

Setup:

1. Open Settings > Integrations > Google Business Profile.
2. Connect a Google account that can access the listing.
3. Select or confirm the business profile.
4. Review connection status.
5. Verify reviews or listing data where the console displays them.

If the connection fails, reconnect with an account that has listing permissions.

What the operator should see:

Google Calendar

Use calendar sync when booking availability needs to respect external calendars.

Setup:

1. Open Scheduling.
2. Open calendar sync.
3. Connect Google Calendar or another supported provider.
4. Select the calendar.
5. Confirm sync status.
6. Test public booking availability.

What the operator should see:

Ownership And Retest

Every enabled Google integration should have:

• A named owner.
• The provider account or property recorded.
• The console card path recorded.
• The public route or workflow used for verification.
• The consent/legal posture recorded.
• A retest date after launch or after campaign changes.

Retest Google settings when the domain changes, the business changes owners, a new ad campaign launches, a booking confirmation page changes, or a calendar owner leaves the company.

Troubleshooting

Google issues are usually split between configuration, consent, and reporting delay. Confirm the console setting first, then inspect whether the public site is allowed to load the tag, and only then compare provider reporting.