Understand external integrations
Understand how an organization connects to calendar, analytics, search, and advertising services.
An integration connects an organization's reservations, website, and operating data to a calendar, analytics, search, or advertising service. Each integration has a provider, status, and provider-specific resource identifiers.
Business value
Integrations connect reservation schedules, customer actions, advertising spend, and operating results to external services. Clear status and ownership help teams compare results. They also keep organization assets safe when staff responsibilities change.
| Operating goal | Integration role | Measure |
|---|---|---|
| Understand customer actions | Send visits and important actions to an analytics service. | Visits, important events, and conversions |
| Share reservation schedules | Copy one organization's reservations to its operations calendar. | Sync delay, missing events, and duplicates |
| Connect advertising results | Relate accounts, campaigns, and leads to operating outcomes. | Cost, leads, reservations, or purchases |
| Manage channel stability | Separate pending, linked, and error states. | Connection errors, recovery time, and test events |
| Disconnect safely | Remove dependent campaigns and external resources in order. | Remaining dependencies, deletion failures, and detached records |
Examples
Example: Measure search advertising reservations. Connect Google Analytics and Google Ads. Verify a test visit and conversion before publication. Compare cost, leads, and completed reservations for the same period.
Example: Connect Meta advertising to message consultations. Connect organization-owned ad and message assets. Test receipt and first response with a synthetic lead. Review leads, first response time, and reservation conversion by campaign.
Example: Review branch reservations in Google Calendar. Connect a different Google primary calendar for each branch. Test synthetic reservation creation, time changes, and cancellation. Review sync delay, missing events, and duplicates.
Supported integrations
| Purpose | Provider | Result to verify |
|---|---|---|
| Reservation schedule | Google Calendar | Creation, changes, and cancellation for one organization |
| Web analytics | Google Analytics | A test visit and event from the public website |
| Search performance | Google Search Console | The correct site property and search data |
| Google advertising | Google Ads | The advertising account, campaigns, and conversions |
| Meta measurement | Meta Pixel | A test event from the public website |
| Meta advertising | Meta Ads | Advertising assets, campaigns, and leads |
| Korean search and advertising | Naver | The connected search or advertising asset |
Manage accounts that exchange customer messages under Customer channels. Review advertising campaigns and conversions under Marketing measurement and campaigns.
Status
| Status | Meaning | Administrator action |
|---|---|---|
| Not connected | The account exists, but provider approval is incomplete. | Complete connection from the account details. |
| Pending | The request is saved while external resources are prepared. | Check the status again after a short wait. |
| Connected | Required external resources and permissions are available. | Test a schedule, event, or campaign result. |
| Error | External permissions or setup did not complete. | Check provider access and the selected account. |
Connect Google Calendar and message channels under Accounts. A calendar account remains not connected until Google approval completes. Analytics and advertising integrations can show Pending while external resources are prepared.
Check before connection
- The current organization or branch matches the external account scope.
- The organization owns the external account and assets.
- The person connecting the account has administrator access in the external service.
- You can separate test events from production events.
Disconnect safely
Delete campaigns that use an advertising integration before you disconnect it. Laney rejects the disconnect while any dependent campaign remains. This order keeps the account information that a campaign needs for external deletion.
After Laney records a delete request, its analytics tag or pixel leaves the website at once. Laney removes the local record only after the external service confirms deletion. A failed confirmation keeps the record visible instead of hiding the error. Check provider access and account status before a retry.
An external resource can remain when its provider has no deletion API. Laney then keeps a detached record but clears its credentials. A later connection to the same provider starts as a new link.