Prerequisites
The connector should already be set up, with a Connector Profile and a Linked Account. See Getting Started on the Google Shopping connector page.How webhooks are set up
This connector uses Programmatic Webhooks. StackOne creates and manages the webhook subscription automatically when the account is connected — there is no webhook screen to configure in Merchant Center and no URL to paste.
Enable the events you need
When the connection is established, StackOne creates one Merchant API notification subscription (POST /notifications/v1/accounts/{account}/notificationsubscriptions) for each webhook event you enable, targeting the Merchant Center ID configured on the connection and delivering to a unique StackOne callback URL.
Unsubscribe
Disabling an event or disconnecting the account deletes the corresponding notification subscription, which stops deliveries.
Available webhook events
The events below can be enabled for this connection. Only the events you select in StackOne are subscribed in Google Merchant Center and delivered.
- Product Status Change (
PRODUCT_STATUS_CHANGE) — Fired when a product’s approval status (approved, pending, disapproved) changes in a reporting context such as Shopping ads or free listings, including when a product is first created or deleted. - Account Service Change (
ACCOUNT_SERVICE_CHANGE) — Fired when an account service relationship on the Merchant Center account is created, updated, or deleted.
Delivery format
How Google delivers events to StackOne.
Inspect event payloads
Google sends each notification as an HTTP POST with a JSON body of the form {"message": {"data": "..."}}, where data is a base64-encoded JSON message. StackOne decodes it and emits the decoded message (account, resource, eventTime, and the status changes or operation) as the event data.
Verify deliveries
Merchant API notifications are not signed. StackOne verifies each delivery through the unique, unguessable callback URL generated for the connection.