Shopee Ads

Shopee Ads is a seller-facing, on-platform ad product. The official Ads site lists Product Search Ads, Shop Search Ads, Discovery Ads, Brand Ads, and other Shopee placements. It also lists Facebook as a separate off-platform product. See the Shopee Ads product page and the official off-platform terms.

The first-party pages checked on 2026-08-30 document ad creation and reporting inside Seller Centre. They do not publish a Shopee Ads event endpoint, event payload, browser tag, or advertiser conversion API. This skill therefore has no Shopee Ads API adapter. It records first-party events locally and uses Seller Centre reporting for Shopee attribution. See Shopee Ads and Monitoring Ads Performance.

Use ad-conversion-hub for the canonical event envelope, consent gate, identity rules, retry policy, and adapter contract. Pair it with ad-experiments for one-audience tests, seed sizing, PII-export authorization, and payment-provider truth.

Account and access

The documented self-serve route is a Shopee seller account. In the official Philippines help page, sellers open Shopee Ads from the Shopee app or click Shopee Ads in the Seller Centre left navigation. See Monitoring Ads Performance.

There is no separate public Shopee Ads developer signup in the first-party pages checked. Do not ask an engineer to create an Ads app, pixel, CTV source, or conversion token. Start with the local Seller Centre route and confirm that the required ad type is available for that seller and market. See Monitoring Ads Performance.

The official Product Search Ads guide shows this setup flow:

1. Select the product to advertise.
2. Choose recommended keywords or set keywords.
3. Set a bid for each keyword.

See Using Product Ads. Do not treat those console actions as a programmable API contract.

Shopee's off-platform terms describe a separate service purchased through Seller Centre. They require an eligible seller account and refer to external channels such as Meta and Google. That service is not a Shopee Ads conversion API. See the Shopee off-platform terms.

Client-side tag or pixel

No public Shopee Ads browser tag, pixel ID, JavaScript SDK, or CTV measurement source is documented in the official Ads pages checked. The pages describe ads that run in Shopee and direct sellers to Shopee's app or Seller Centre for performance data. See Shopee Ads and Monitoring Ads Performance.

Do not add any of these assumed settings:

SHOPEE_ADS_PIXEL_ID
SHOPEE_ADS_TAG_ID
SHOPEE_ADS_CTV_ID

On your own website, use only the analytics and consent controls already defined by the hub. A local page_view, view_content, lead, or checkout event measures your site. It does not send a Shopee Ads conversion.

Rule setup and event mapping

Shopee's published conversion metric is tied to products and orders in Shopee. In the Philippines help page, a conversion means a unique product sold in an order. Items sold means the quantity of products. Orders means the number of orders. See the metric definitions.

Do not model Shopee Ads as a generic web conversion-rule API. Keep the hub taxonomy for first-party measurement, then map it to local evidence:

Shopee's standard click attribution in the Philippines help page covers orders within seven days of an ad click. Its GMV Max view attribution covers orders within one day of an eligible product view. Treat these as the documented Philippines windows, not a universal cross-market contract. See Monitoring Ads Performance.

Server-side conversions API

No public Shopee Ads conversions API is documented in the first-party sources checked. The official pages publish campaign types, setup instructions, and Seller Centre metrics. They do not publish a Shopee Ads conversion endpoint, HTTP method, authentication header, request schema, timestamp field, identity field, or deduplication field. See Shopee Ads and Monitoring Ads Performance.

Do not implement or probe guessed paths such as /conversions, /events, or /pixel. Do not send hashed email, phone, payment data, or a hub event ID to the Shopee Open Platform as an assumed Ads event. No first-party Ads source checked authorizes that behavior. See Shopee Ads and Monitoring Ads Performance.

The Shopee Open API developer guide is a separate app and shop-authorization workflow. It describes developer accounts, apps, shop authorization, and merchant operations. It does not provide a Shopee Ads conversion contract. See the Shopee Open API developer guide.

If Shopee supplies a private partner feed for a specific agreement, keep the adapter disabled until the current contract supplies all of these details:

• endpoint and HTTP method;
• authentication and secret rotation;
• request fields and timestamp units;
• accepted identity fields and hashing rules;
• retry, retention, and deduplication rules;
• response states and reporting join key.

Record those details in the partner documentation for that campaign. Do not promote them into this public skill from an email or an undocumented console.

Identity and consent

The first-party Ads pages checked do not document a Shopee Ads customer-list upload, hashed-email field, phone field, or server-side identity match rule. Therefore this adapter sends no customer identifiers to Shopee Ads.

Gate owned-site measurement through the hub's consent model. Keep any local identity normalization inside the hub. Hash an identifier only when a documented destination requires it and the consent decision permits ad-user data. No Shopee-specific hashing rule belongs here. See Shopee Ads and Monitoring Ads Performance.

Do not infer identity matching from Seller Centre's aggregate ad metrics. A Shopee dashboard count is platform reporting, not proof that a customer identifier was accepted from your server.

Click ID and first-party cookie

The official Ads pages checked do not document a Shopee-owned click parameter, cookie name, first-party cookie lifetime, or external attribution join key. Do not create names such as shopee_click_id, shopee_id, or sp_click_id. See Shopee Ads and Monitoring Ads Performance.

Shopee's documented attribution is internal to its ads and order measurement. In the Philippines help page, click and GMV Max view windows are defined by the Shopee campaign interaction. See the published attribution definitions.

You may capture ordinary first-party campaign parameters on your own website when your campaign link supplies them. Use only the names present in the actual link. Store approved values under your own namespace, apply the hub's consent rules, and attach them to the canonical event. Do not claim that Shopee will read or join those values.

Deduplication

Shopee publishes no browser/server event pair or deduplication field in the first-party Ads sources checked. There is no Shopee-specific deduplication implementation for this adapter. See Shopee Ads and Monitoring Ads Performance.

Use the hub's canonical event ID for your own event store and payment reconciliation. Make retries idempotent in your system. Do not send that ID to Shopee as a guessed parameter, and do not count a local event as a Shopee Ads conversion.

Seller Centre settings that override code

Shopee's console controls the campaign configuration. Code cannot override these settings through a documented Ads API. See Shopee Ads and Monitoring Ads Performance.

• Product Search Ads use a selected product, keywords, and keyword bids. See Product Search Ads.
• Homepage Brand Ads use a budget, duration, billing details, and uploaded banner creative. The official guide describes CPM billing for this format. See Homepage Brand Ads.
• Shop Search Ads may be automatically available only to selected sellers with good sales and order ratings. See Shop Search Ads.
• Shopee exposes separate on-platform and off-platform ad products. Do not assume that settings for a Facebook placement apply to an on-platform Shopee campaign. See Shopee Ads and the off-platform terms.

Verify the local market's available ad types, billing, eligibility, and campaign settings in Seller Centre before spend. The cited product pages are market-specific and do not establish universal settings for every Shopee market.

Verification

Use two separate proofs:

1. First-party proof: record the owned-site request, consent decision, canonical event ID, and payment or signup result in your server logs.
2. Shopee proof: open the Shopee app or Seller Centre and review the ad performance metrics for the campaign. The official Philippines guide gives those navigation paths. See Monitoring Ads Performance.

Shopee processes checkout and payment for on-platform orders, so there is no separate external payment provider to reconcile against for those sales. Reconcile orders, sales, and refunds against Shopee's Confirmed order and settlement data instead. Do not treat Shopee's Placed numbers as settled revenue. Shopee defines placed sales as the order value at checkout, including paid and unpaid orders. It defines confirmed sales separately. See Placed and Confirmed metrics.

For the Philippines page checked, the dashboard can export data for up to the last 90 days. Keep a dated export with the campaign ID, market, time zone, and report filters used. See Checking performance and export limits.

A successful page view, local event, or Seller Centre login does not prove that Shopee credited a sale. Attribution proof comes from the platform report and must be compared with your own order truth.

Common pitfalls and security

• Do not use open.shopee.com merchant APIs as an Ads conversion API. The official Open API guide documents a separate app and shop workflow. See the Open API guide.
• Do not invent an Ads endpoint, bearer token, pixel ID, click ID, cookie, or payload field. The first-party Ads pages checked publish none of these contracts. See Shopee Ads and Monitoring Ads Performance.
• Do not equate a Shopee Conversion with a website purchase. Shopee defines it as a unique product sold in an order. See metric definitions.
• Do not mix Placed and Confirmed metrics. A placed order can include an unpaid checkout. See Placed and Confirmed metrics.
• Do not generalize the Philippines attribution windows to another market. Confirm the local Seller Centre rules before reporting performance. See the Philippines attribution page.
• Keep any credentials for your own backend or an approved partner in the server secret store. Never put secrets in browser bundles, URLs, logs, screenshots, or commits.
• Apply the hub consent gate before first-party measurement. Keep the adapter a logged no-op when no approved Shopee contract exists. It must not fail a checkout or payment webhook.

Hub conventions

Pair this adapter with ad-conversion-hub and the experiment policy used by the application. The hub owns the event envelope, consent gate, local identity handling, retry policy, and payment truth. This adapter owns only the documented Shopee campaign and reporting facts.

The adapter's safe default is:

Shopee Ads server dispatch: disabled
Shopee browser tag: absent
Shopee click-ID parsing: absent
Shopee customer-list upload: absent
Shopee proof: Seller Centre report plus first-party reconciliation

Official sources checked (2026-08-30)

• Shopee Ads
• Monitoring Ads Performance
• Using Product Ads
• Homepage Brand Ads
• Shop Search Ads
• Shopee off-platform advertising terms
• Shopee Open API developer guide