diff --git a/docs.json b/docs.json index 05eea86..4b461f8 100644 --- a/docs.json +++ b/docs.json @@ -95,7 +95,8 @@ { "group": "Ecommerce Manager", "pages": [ - "ecommerce-manager/meta-commerce-manager" + "ecommerce-manager/meta-commerce-manager", + "ecommerce-manager/google-commerce-manager" ] }, { @@ -228,6 +229,10 @@ { "source": "/web-to-app/google", "destination": "/ad-networks/google-web-to-app" + }, + { + "source": "/ecommerce-manager/google-merchant-center", + "destination": "/ecommerce-manager/google-commerce-manager" } ] } diff --git a/ecommerce-manager/google-commerce-manager.mdx b/ecommerce-manager/google-commerce-manager.mdx new file mode 100644 index 0000000..394ec20 --- /dev/null +++ b/ecommerce-manager/google-commerce-manager.mdx @@ -0,0 +1,238 @@ +--- +title: "Google Commerce Manager" +description: "Setting up Google Commerce Manager with Google Ads for ecommerce tracking and attribution via Linkrunner." +icon: "google" +--- + +## Overview + +Google Merchant Center lets you upload your product catalog so it can appear across Google surfaces — Search, Shopping, Display, and more. To run Shopping or Performance Max campaigns, you need to link your Merchant Center account to Google Ads and have your products approved. Once that's done, you can start sending ecommerce event data through Linkrunner for proper attribution. + + +**Before you begin, make sure you have:** +- A Google Ads account set up and linked to Linkrunner (see [Google Ads setup](/ad-networks/google-ads)) +- Products ready to upload to Google Merchant Center + + +## Step 1: Create a Google Merchant Center Account and Link to Google Ads + +First, create your Google Merchant Center account at [merchant.google.com](https://business.google.com/in/merchant-center). During setup, you'll provide your business name, website URL, and country. + +Once your account is created, you need to link it to your Google Ads account so your product data can be used in campaigns. + +Google Merchant Center account setup and linking to Google Ads + +To link your accounts: + +1. In Google Merchant Center, go to **Settings** → **Linked accounts**. +2. Under **Google Ads**, click **Link account**. +3. Enter your Google Ads customer ID and send the link request. +4. In Google Ads, go to **Tools** → **Linked accounts** → **Google Merchant Center** and approve the request. + +Linking Google Merchant Center with Google Ads account + +Once linked, your product catalog will be available to use in Google Ads campaigns like Shopping and Performance Max. + +## Step 2: Add Products to Google Merchant Center + +With your account set up and linked, the next step is adding your products. You can do this manually, via a spreadsheet feed, or through a scheduled data feed URL. + +Adding products to Google Merchant Center + +When adding products, make sure to fill in all required attributes: + +- **Title** — clear, descriptive product name +- **Description** — accurate product details +- **Link** — the product page URL on your website +- **Image link** — high-quality product image URL +- **Price** — must match the price on your website +- **Availability** — `in stock`, `out of stock`, or `preorder` +- **Brand**, **GTIN** or **MPN** — for product identification + +After uploading, Google will review your products. This typically takes **1–3 business days**. You can monitor the status in **Products** → **All products** in Merchant Center. + +## Step 3: Match Product IDs with Your Backend + +This is a critical step. The product IDs in Google Merchant Center must exactly match the product IDs you use in your backend and send through Linkrunner events. + +Product ID mapping between Google Merchant Center and your backend + +In Google Merchant Center, each product has an **ID** (also called `offer_id`). This is the value you'll use when sending ecommerce events through Linkrunner. If these IDs don't match, Google won't be able to attribute events back to the correct products. + + +Make sure the product `id` you send in your Linkrunner events exactly matches the **ID (`offer_id`)** of the product in Google Merchant Center. A mismatch will break product attribution and lower your campaign performance. + + +## Step 4: Event Mapping + +Once your products are approved and your campaign is live, you need to map your custom app events to the standard Google ecommerce events in the Linkrunner Dashboard. This tells Linkrunner which of your events correspond to which Google conversion actions. + +There are **3 essential events** to map: + +- Your view item event (e.g., `view_item`, `item_viewed`) → maps to **`view_item`** +- Your add to cart event (e.g., `add_to_cart`) → maps to **`add_to_cart`** +- Your purchase event (e.g., `FIRST_PAYMENT`, `DEFAULT`) → maps to **`ecommerce_purchase`** + +_In the Linkrunner Dashboard, go to your Google Ads integration settings and map each of your custom event names to the corresponding standard Google event._ + +## Understanding `event_data` for Google + +When sending events via the [Capture Event API](/api-reference/event-capture), [Capture Payment API](/api-reference/revenue-tracking), or the Linkrunner SDK (`trackEvent` and `capturePayment` methods), you need to include specific fields in `event_data` so Google can correctly attribute conversions and match products in your Merchant Center catalog. + +### Required Fields + +| Parameter | Type | Required for | Description | +| ------------- | ------ | ----------------------------------------- | --------------------------------------------------------------------------- | +| `content_ids` | array | `view_item`, `add_to_cart`, `ecommerce_purchase` | Product IDs — must exactly match the **ID (`offer_id`)** in Google Merchant Center | +| `value` | number | `add_to_cart`, `ecommerce_purchase` | Total revenue value. No currency symbols. | +| `currency` | string | `add_to_cart`, `ecommerce_purchase` | 3-letter ISO currency code (e.g., `"INR"`, `"USD"`) | +| `num_items` | number | `add_to_cart`, `ecommerce_purchase` | Total quantity of items | +| `order_id` | string | `ecommerce_purchase` | Unique order ID from your backend | + +### view_item + +Fired when a user views a product page. + + + +```javascript SDK +await linkrunner.trackEvent( + "view_item", // Map this custom event to "view_item" in the Linkrunner Dashboard + { + content_ids: ["sku_blue_tshirt"], // Must match Merchant Center ID (offer_id) + }, +); +``` + +```json API +// POST /capture-event +{ + "token": "your_project_token", + "event_name": "view_item", + "user_id": "user_123", + "install_instance_id": "abc-123", + "event_data": { + "content_ids": ["sku_blue_tshirt"] // Must match Merchant Center ID (offer_id) + } +} +``` + + + +### add_to_cart + +Fired when a user adds a product to their cart. + + + +```javascript SDK +await linkrunner.trackEvent( + "add_to_cart", // Map this custom event to "add_to_cart" in the Linkrunner Dashboard + { + content_ids: ["sku_blue_tshirt"], // Must match Merchant Center ID (offer_id) + value: 1598, // Required — total value (Google uses this as revenue) + currency: "INR", // Required + num_items: 2, // Required + }, +); +``` + +```json API +// POST /capture-event +{ + "token": "your_project_token", + "event_name": "add_to_cart", + "user_id": "user_123", + "install_instance_id": "abc-123", + "event_data": { + "content_ids": ["sku_blue_tshirt"], // Must match Merchant Center ID (offer_id) + "value": 1598, // Required — total value (Google uses this as revenue) + "currency": "INR", // Required + "num_items": 2 // Required + } +} +``` + + + +### ecommerce_purchase + +Fired when a user completes a purchase. + + + +```javascript SDK +await linkrunner.capturePayment({ + amount: 2298.00, + userId: "user_456", + paymentId: "order_98765", + type: "FIRST_PAYMENT", // Map this payment type to "ecommerce_purchase" in the Linkrunner Dashboard + status: "PAYMENT_COMPLETED", + eventData: { + content_ids: ["sku_blue_tshirt", "sku_red_shoes"], // Must match Merchant Center ID (offer_id) + value: 2298, // Required + currency: "INR", // Required + num_items: 2, // Required + order_id: "order_98765", // Required for purchase events + }, +}); +``` + +```json API +// POST /capture-payment +{ + "token": "your_project_token", + "payment_id": "order_98765", + "user_id": "user_456", + "amount": 2298.00, + "type": "FIRST_PAYMENT", + "status": "PAYMENT_COMPLETED", + "install_instance_id": "abc-123", + "event_data": { + "content_ids": ["sku_blue_tshirt", "sku_red_shoes"], // Must match Merchant Center ID (offer_id) + "value": 2298, + "currency": "INR", + "num_items": 2, + "order_id": "order_98765" + } +} +``` + + + +_The SDK examples above use React Native syntax. The same `eventData` fields apply across all SDKs — for platform-specific examples, refer to the Ecommerce Events section in each SDK guide: [React Native](/sdk/react-native#ecommerce-events), [Flutter](/sdk/flutter#ecommerce-events), [iOS](/sdk/ios#ecommerce-events), [Android](/sdk/android#ecommerce-events)._ + + +The `content_ids` you send must exactly match the **ID (`offer_id`)** of the product in Google Merchant Center (the same ID from Step 3). If they don't match, Google won't be able to link the conversion back to the correct product in your catalog. + + + +The `amount` field in `capturePayment` and the `value` field in `event_data` should be consistent — both represent the total order value. Google reads `value` from `event_data` for conversion reporting. + + +## Verifying Events in Google Ads + +Once you start sending events through Linkrunner, you can verify they're being received in Google Ads under **Goals → Summary**. You'll see your mapped conversion actions (`view_item`, `add_to_cart`, `ecommerce_purchase`) listed there with their recorded conversion counts. + +Google Ads Goals Summary showing ecommerce conversion events + +It can take up to **24 hours** for conversion data to appear after your first events are sent. If you don't see data after that window, double-check your event mapping in the Linkrunner Dashboard and verify the `content_ids` match your Merchant Center catalog. + +--- + +> **Note:** The `event_data` fields above can be sent via the Linkrunner SDK (`trackEvent` and `capturePayment` methods) or directly via the APIs. For full request schemas, refer to the [Capture Event API](/api-reference/event-capture) and [Capture Payment API](/api-reference/revenue-tracking) documentation. diff --git a/images/ecommerce-event-google/ecommerce-1.png b/images/ecommerce-event-google/ecommerce-1.png new file mode 100644 index 0000000..6485fdb Binary files /dev/null and b/images/ecommerce-event-google/ecommerce-1.png differ diff --git a/images/ecommerce-event-google/ecommerce-2.png b/images/ecommerce-event-google/ecommerce-2.png new file mode 100644 index 0000000..a8da2ed Binary files /dev/null and b/images/ecommerce-event-google/ecommerce-2.png differ diff --git a/images/ecommerce-event-google/ecommerce-3.png b/images/ecommerce-event-google/ecommerce-3.png new file mode 100644 index 0000000..a2cb793 Binary files /dev/null and b/images/ecommerce-event-google/ecommerce-3.png differ diff --git a/images/ecommerce-event-google/ecommerce-4.png b/images/ecommerce-event-google/ecommerce-4.png new file mode 100644 index 0000000..3d6538f Binary files /dev/null and b/images/ecommerce-event-google/ecommerce-4.png differ diff --git a/images/ecommerce-event-google/ecommerce-5.png b/images/ecommerce-event-google/ecommerce-5.png new file mode 100644 index 0000000..07aec74 Binary files /dev/null and b/images/ecommerce-event-google/ecommerce-5.png differ diff --git a/images/ecommerce-event-google/ecommerce-6.png b/images/ecommerce-event-google/ecommerce-6.png new file mode 100644 index 0000000..cbe27a3 Binary files /dev/null and b/images/ecommerce-event-google/ecommerce-6.png differ diff --git a/sdk/android.mdx b/sdk/android.mdx index b757743..eeca7b1 100644 --- a/sdk/android.mdx +++ b/sdk/android.mdx @@ -497,9 +497,9 @@ private fun trackPurchaseEvent() { > **Minimum SDK Version:** Ecommerce Event Manager requires `linkrunner-android` **v3.6.0** or above. Please ensure your SDK is updated before using this feature. -If you are tracking Ecommerce events to sync with Meta Catalog Sales, you must format your `eventData` to include Meta's required fields. **You also need to map your custom event to the standard commerce event in the Linkrunner Dashboard.** +If you are tracking Ecommerce events to sync with Meta or Google, you must format your `eventData` to include the required fields. **You also need to map your custom event to the standard commerce event in the Linkrunner Dashboard.** -For detailed explanations of the required fields like `content_ids`, `contents`, and `value`, refer to our [Meta Commerce Manager documentation](/ecommerce-manager/meta-commerce-manager#understanding-event_data). +For detailed explanations of the required fields like `content_ids`, `contents`, and `value`, refer to our [Meta Commerce Manager documentation](/ecommerce-manager/meta-commerce-manager#understanding-event_data) or [Google Commerce Manager documentation](/ecommerce-manager/google-commerce-manager#understanding-event_data-for-google). ### Add To Cart Example @@ -509,7 +509,7 @@ Use the `trackEvent` method to send an `AddToCart` event: private fun trackAddToCart() { CoroutineScope(Dispatchers.IO).launch { LinkRunner.getInstance().trackEvent( - eventName = "add_to_cart", // Map this custom event to "AddToCart" in the Linkrunner Dashboard + eventName = "add_to_cart", // Your custom event name — map to "AddToCart" (Meta) or "add_to_cart" (Google) in the Linkrunner Dashboard. See: /ecommerce-manager/meta-commerce-manager, /ecommerce-manager/google-commerce-manager eventData = mapOf( "content_ids" to listOf("product_123"), "contents" to listOf( @@ -537,7 +537,7 @@ Use the `trackEvent` method to send a `ViewContent` event: private fun trackViewContent() { CoroutineScope(Dispatchers.IO).launch { LinkRunner.getInstance().trackEvent( - eventName = "view_item", // Map this custom event to "ViewContent" in the Linkrunner Dashboard + eventName = "view_item", // Your custom event name — map to "ViewContent" (Meta) or "view_item" (Google) in the Linkrunner Dashboard. See: /ecommerce-manager/meta-commerce-manager, /ecommerce-manager/google-commerce-manager eventData = mapOf( "content_ids" to listOf("product_123"), "contents" to listOf( @@ -569,7 +569,7 @@ private fun capturePurchase() { paymentId = "payment_456", userId = "user123", amount = 49.99, - type = PaymentType.FIRST_PAYMENT, // Map this payment type to "Purchase" in the Linkrunner Dashboard + type = PaymentType.FIRST_PAYMENT, // Your payment type — map to "Purchase" (Meta) or "ecommerce_purchase" (Google) in the Linkrunner Dashboard. See: /ecommerce-manager/meta-commerce-manager, /ecommerce-manager/google-commerce-manager status = PaymentStatus.PAYMENT_COMPLETED, eventData = mapOf( "content_ids" to listOf("product_123"), @@ -595,7 +595,7 @@ private fun capturePurchase() { } ``` -> **Note:** For more information on testing and verifying your ecommerce events, please see our [Testing Ecommerce Events](/ecommerce-manager/meta-commerce-manager#testing-ecommerce-events) guide. +> **Note:** For more information on testing and verifying your ecommerce events, please see our [Meta Commerce Manager](/ecommerce-manager/meta-commerce-manager#testing-ecommerce-events) or [Google Commerce Manager](/ecommerce-manager/google-commerce-manager#verifying-events-in-google-ads) guide. ## Enhanced Privacy Controls diff --git a/sdk/flutter.mdx b/sdk/flutter.mdx index 18c0908..7c40199 100644 --- a/sdk/flutter.mdx +++ b/sdk/flutter.mdx @@ -398,7 +398,7 @@ Future capturePayment() async { - `PaymentStatus.PAYMENT_COMPLETED` - Payment completed successfully (default if not specified) - `PaymentStatus.PAYMENT_FAILED` - Payment attempt failed - `PaymentStatus.PAYMENT_CANCELLED` - Payment was cancelled -- `eventData`: `Map` (optional) - Key-value pairs for additional event data, including Meta ecommerce properties. +- `eventData`: `Map` (optional) - Key-value pairs for additional event data, including ecommerce properties for Meta and Google. ### Removing Payments @@ -431,9 +431,9 @@ Note: Either `paymentId` or `userId` must be provided when calling `removePaymen > **Minimum SDK Version:** Ecommerce Event Manager requires `linkrunner-flutter` **v3.7.0** or above. Please ensure your SDK is updated before using this feature. -If you are tracking Ecommerce events to sync with Meta Catalog Sales, you must format your `eventData` to include Meta's required fields. **You also need to map your custom event to the standard commerce event in the Linkrunner Dashboard.** +If you are tracking Ecommerce events to sync with Meta or Google, you must format your `eventData` to include the required fields. **You also need to map your custom event to the standard commerce event in the Linkrunner Dashboard.** -For detailed explanations of the required fields like `content_ids`, `contents`, and `value`, refer to our [Meta Commerce Manager documentation](/ecommerce-manager/meta-commerce-manager#understanding-event_data). +For detailed explanations of the required fields like `content_ids`, `contents`, and `value`, refer to our [Meta Commerce Manager documentation](/ecommerce-manager/meta-commerce-manager#understanding-event_data) or [Google Commerce Manager documentation](/ecommerce-manager/google-commerce-manager#understanding-event_data-for-google). ### Add To Cart Example @@ -443,7 +443,7 @@ Use the `trackEvent` method to send an `AddToCart` event: Future trackAddToCart() async { try { await LinkRunner().trackEvent( - eventName: 'add_to_cart', // Map this custom event to "AddToCart" in the Linkrunner Dashboard + eventName: 'add_to_cart', // Your custom event name — map to "AddToCart" (Meta) or "add_to_cart" (Google) in the Linkrunner Dashboard. See: /ecommerce-manager/meta-commerce-manager, /ecommerce-manager/google-commerce-manager eventData: { 'content_ids': ['product_123'], 'contents': [ @@ -474,7 +474,7 @@ Use the `trackEvent` method to send a `ViewContent` event: Future trackViewContent() async { try { await LinkRunner().trackEvent( - eventName: 'view_item', // Map this custom event to "ViewContent" in the Linkrunner Dashboard + eventName: 'view_item', // Your custom event name — map to "ViewContent" (Meta) or "view_item" (Google) in the Linkrunner Dashboard. See: /ecommerce-manager/meta-commerce-manager, /ecommerce-manager/google-commerce-manager eventData: { 'content_ids': ['product_123'], 'contents': [ @@ -509,7 +509,7 @@ Future capturePurchase() async { amount: 49.99, userId: 'user123', paymentId: 'payment_456', - type: PaymentType.FIRST_PAYMENT, // Map this payment type to "Purchase" in the Linkrunner Dashboard + type: PaymentType.FIRST_PAYMENT, // Your payment type — map to "Purchase" (Meta) or "ecommerce_purchase" (Google) in the Linkrunner Dashboard. See: /ecommerce-manager/meta-commerce-manager, /ecommerce-manager/google-commerce-manager status: PaymentStatus.PAYMENT_COMPLETED, eventData: { 'content_ids': ['product_123'], @@ -535,7 +535,7 @@ Future capturePurchase() async { } ``` -> **Note:** For more information on testing and verifying your ecommerce events, please see our [Testing Ecommerce Events](/ecommerce-manager/meta-commerce-manager#testing-ecommerce-events) guide. +> **Note:** For more information on testing and verifying your ecommerce events, please see our [Meta Commerce Manager](/ecommerce-manager/meta-commerce-manager#testing-ecommerce-events) or [Google Commerce Manager](/ecommerce-manager/google-commerce-manager#verifying-events-in-google-ads) guide. ## Tracking Custom Events diff --git a/sdk/ios.mdx b/sdk/ios.mdx index 45f764e..5381554 100644 --- a/sdk/ios.mdx +++ b/sdk/ios.mdx @@ -402,9 +402,9 @@ func trackPurchaseEvent() async { > **Minimum SDK Version:** Ecommerce Event Manager requires `linkrunner-ios` **v3.8.0** or above. Please ensure your SDK is updated before using this feature. -If you are tracking Ecommerce events to sync with Meta Catalog Sales, you must format your `eventData` to include Meta's required fields. **You also need to map your custom event to the standard commerce event in the Linkrunner Dashboard.** +If you are tracking Ecommerce events to sync with Meta or Google, you must format your `eventData` to include the required fields. **You also need to map your custom event to the standard commerce event in the Linkrunner Dashboard.** -For detailed explanations of the required fields like `content_ids`, `contents`, and `value`, refer to our [Meta Commerce Manager documentation](/ecommerce-manager/meta-commerce-manager#understanding-event_data). +For detailed explanations of the required fields like `content_ids`, `contents`, and `value`, refer to our [Meta Commerce Manager documentation](/ecommerce-manager/meta-commerce-manager#understanding-event_data) or [Google Commerce Manager documentation](/ecommerce-manager/google-commerce-manager#understanding-event_data-for-google). ### Add To Cart Example @@ -414,7 +414,7 @@ Use the `trackEvent` method to send an `AddToCart` event: func trackAddToCart() async { do { try await LinkrunnerSDK.shared.trackEvent( - eventName: "add_to_cart", // Map this custom event to "AddToCart" in the Linkrunner Dashboard + eventName: "add_to_cart", // Your custom event name — map to "AddToCart" (Meta) or "add_to_cart" (Google) in the Linkrunner Dashboard. See: /ecommerce-manager/meta-commerce-manager, /ecommerce-manager/google-commerce-manager eventData: [ "content_ids": ["product_123"], "contents": [ @@ -445,7 +445,7 @@ Use the `trackEvent` method to send a `ViewContent` event: func trackViewContent() async { do { try await LinkrunnerSDK.shared.trackEvent( - eventName: "view_item", // Map this custom event to "ViewContent" in the Linkrunner Dashboard + eventName: "view_item", // Your custom event name — map to "ViewContent" (Meta) or "view_item" (Google) in the Linkrunner Dashboard. See: /ecommerce-manager/meta-commerce-manager, /ecommerce-manager/google-commerce-manager eventData: [ "content_ids": ["product_123"], "contents": [ @@ -479,7 +479,7 @@ func capturePurchase() async { amount: 49.99, userId: "user123", paymentId: "payment_456", - type: .firstPayment, // Map this payment type to "Purchase" in the Linkrunner Dashboard + type: .firstPayment, // Your payment type — map to "Purchase" (Meta) or "ecommerce_purchase" (Google) in the Linkrunner Dashboard. See: /ecommerce-manager/meta-commerce-manager, /ecommerce-manager/google-commerce-manager status: .completed, eventData: [ "content_ids": ["product_123"], @@ -504,7 +504,7 @@ func capturePurchase() async { } ``` -> **Note:** For more information on testing and verifying your ecommerce events, please see our [Testing Ecommerce Events](/ecommerce-manager/meta-commerce-manager#testing-ecommerce-events) guide. +> **Note:** For more information on testing and verifying your ecommerce events, please see our [Meta Commerce Manager](/ecommerce-manager/meta-commerce-manager#testing-ecommerce-events) or [Google Commerce Manager](/ecommerce-manager/google-commerce-manager#verifying-events-in-google-ads) guide. ## Enhanced Privacy Controls diff --git a/sdk/react-native.mdx b/sdk/react-native.mdx index 3d9600f..970571c 100644 --- a/sdk/react-native.mdx +++ b/sdk/react-native.mdx @@ -264,7 +264,7 @@ const capturePayment = async () => { - `PAYMENT_COMPLETED` - Payment completed successfully (default if not specified) - `PAYMENT_FAILED` - Payment attempt failed - `PAYMENT_CANCELLED` - Payment was cancelled -- `eventData`: object (optional) - Key-value pairs for additional event data, including Meta ecommerce properties. +- `eventData`: object (optional) - Key-value pairs for additional event data, including ecommerce properties for Meta and Google. ### Removing Payments @@ -290,9 +290,9 @@ Note: Either `paymentId` or `userId` must be provided when calling `removePaymen > **Minimum SDK Version:** Ecommerce Event Manager requires `react-native-linkrunner` **v2.7.0** or above. Please ensure your SDK is updated before using this feature. -If you are tracking Ecommerce events to sync with Meta Catalog Sales, you must format your `eventData` to include Meta's required fields. **You also need to map your custom event to the standard commerce event in the Linkrunner Dashboard.** +If you are tracking Ecommerce events to sync with Meta or Google, you must format your `eventData` to include the required fields. **You also need to map your custom event to the standard commerce event in the Linkrunner Dashboard.** -For detailed explanations of the required fields like `content_ids`, `contents`, and `value`, refer to our [Meta Commerce Manager documentation](/ecommerce-manager/meta-commerce-manager#understanding-event_data). +For detailed explanations of the required fields like `content_ids`, `contents`, and `value`, refer to our [Meta Commerce Manager documentation](/ecommerce-manager/meta-commerce-manager#understanding-event_data) or [Google Commerce Manager documentation](/ecommerce-manager/google-commerce-manager#understanding-event_data-for-google). ### Add To Cart Example @@ -302,7 +302,7 @@ Use the `trackEvent` method to send an `AddToCart` event: const trackAddToCart = async () => { try { await linkrunner.trackEvent( - "add_to_cart", // Map this custom event to "AddToCart" in the Linkrunner Dashboard + "add_to_cart", // Your custom event name — map to "AddToCart" (Meta) or "add_to_cart" (Google) in the Linkrunner Dashboard. See: /ecommerce-manager/meta-commerce-manager, /ecommerce-manager/google-commerce-manager { content_ids: ["product_123"], contents: [ @@ -333,7 +333,7 @@ Use the `trackEvent` method to send a `ViewContent` event: const trackViewContent = async () => { try { await linkrunner.trackEvent( - "view_item", // Map this custom event to "ViewContent" in the Linkrunner Dashboard + "view_item", // Your custom event name — map to "ViewContent" (Meta) or "view_item" (Google) in the Linkrunner Dashboard. See: /ecommerce-manager/meta-commerce-manager, /ecommerce-manager/google-commerce-manager { content_ids: ["product_123"], contents: [ @@ -367,7 +367,7 @@ const capturePurchase = async () => { amount: 49.99, userId: "user123", paymentId: "payment_456", - type: "FIRST_PAYMENT", // Map this payment type to "Purchase" in the Linkrunner Dashboard + type: "FIRST_PAYMENT", // Your payment type — map to "Purchase" (Meta) or "ecommerce_purchase" (Google) in the Linkrunner Dashboard. See: /ecommerce-manager/meta-commerce-manager, /ecommerce-manager/google-commerce-manager status: "PAYMENT_COMPLETED", eventData: { content_ids: ["product_123"], @@ -392,7 +392,7 @@ const capturePurchase = async () => { }; ``` -> **Note:** For more information on testing and verifying your ecommerce events, please see our [Testing Ecommerce Events](/ecommerce-manager/meta-commerce-manager#testing-ecommerce-events) guide. +> **Note:** For more information on testing and verifying your ecommerce events, please see our [Meta Commerce Manager](/ecommerce-manager/meta-commerce-manager#testing-ecommerce-events) or [Google Commerce Manager](/ecommerce-manager/google-commerce-manager#verifying-events-in-google-ads) guide. ## Tracking Custom Events