Track Purchase

1. Create the Purchase conversion action in Google Ads

Before AdsPing can forward a Purchase to Google Ads, the conversion action has to exist on the Google Ads side. We’ll create one now, screen by screen. The most important step is choosing the right data source — pick “website” and only website. Other data sources (phone calls from ads, mobile app installs, offline uploads) are managed by Google natively and AdsPing cannot drive them; conversion events fired from a website to those types are silently dropped.

Skip this section if you already have a Purchase conversion action set up that uses the website data source — jump to step 2.

1. 1.1 — Sign in to ads.google.com

   Open ads.google.com and sign in with a Google account that has Admin or Standard access to your Google Ads account. Read-only access will not let you create a conversion action.

   If you have multiple Google Ads accounts, switch to the correct one from the top-right account picker. The 10-digit Customer ID at the top right (format: 123-456-7890) tells you which account you’re in.

2. 1.2 — Open the Conversions page

   In the left navigation, click Goals (Hedefler) → Conversions (Dönüşümler) → Summary (Özet).

   On older / classic Google Ads UI: top-right Tools gear icon → Conversions.

3. 1.3 — Click “+ New conversion action”

   The blue + New conversion action button (“+ Yeni dönüşüm işlemi”) is at the top of the Conversions list. Click it.

4. 1.4 — Pick “Website” as the data sourceMost important step

   Google shows a list of data sources. Pick Website (“Web sitesi”): the source for conversions that happen on the merchant’s own site. This is the only source AdsPing forwards to.

   ✓ Pick this one

   Website — Web sitesi

   Conversions that happen on your website (form submits, purchases, button clicks). AdsPing fires events from your site to this source.

   ✗ Do NOT pick any of these

   • Phone calls (Telefon araması) — from ads: Google’s call-tracking infrastructure (call extensions, forwarding numbers). AdsPing cannot fire events to this source — Google manages it natively. Conversion events fired from a website to a phone-from-ads source are silently dropped.
   • App (Uygulama): Mobile app installs and in-app events. These fire from a mobile SDK (Firebase / Google Play), not from a website. AdsPing is a web tracking platform.
   • Import (İçeri aktar) — offline / CSV / Salesforce: Conversions you manually upload from a spreadsheet or CRM. Different upload mechanism, not what AdsPing does.
   • Google Analytics 4 (GA4): Conversions you’ve already configured as goals in GA4. If you want GA4 forwarding too, AdsPing handles it as a separate destination — not through this Google Ads action.

   Once you’ve clicked Website, click Save and continue.

5. 1.5 — Pick the conversion category: Purchase (Satın alma işlemi)

   Google now shows a list of category cards (“Dönüşümlerinizi gruplandïrïn”). Each card represents a goal Smart Bidding optimizes for. Pick the one that matches what you’re tracking:

   Satın alma işlemi — Purchase

   “Bir kullanıcının satın alma veya ödeme işlemi tamamlamasıdır.”

   In English Google Ads UI: Purchase.

   Click Save and continue.

6. 1.6 — Recommended settings on the details page

   Fill the conversion-action detail form. Recommended values:

   • · Conversion name (Dönüşüm adı): “Purchase — [your store name]”. Use a unique name so you can pick it from a list later in AdsPing.
   • · Value (Değer): Use different values for each conversion (Her dönüşüm için farklı değerler kullan). AdsPing will send the real order total per event; Smart Bidding needs this to optimize revenue.
   • · Count (Say): Every (Her) — if a customer places two orders, count both. (Pick “One” only if you want to count a single conversion per click; ecommerce wants Every.)
   • · Click-through conversion window (Tıklama sonrası dönüşüm penceresi): 30 days (default). Keep at 30 unless your business is unusually long-cycle.
   • · View-through conversion window (Görüntüleme sonrası dönüşüm penceresi): 1 day (default).
   • · Attribution model (İlişkilendirme modeli): Data-driven (Veriye dayalı) — Google’s default, most accurate. Only fall back to Last-click if your account doesn’t have enough data yet (Google will say so).
   • · Include in “Conversions” (Dönüşümler kategorisine dahil et): Yes — needed so Smart Bidding uses this signal.

   Click Done (Bitti), then Save and continue (Kaydet ve devam).

7. 1.7 — Skip the tag-setup screen

   Google now offers three ways to install a tag: Google tag, Google Tag Manager, or Email the tag to your webmaster. You don’t need any of them — AdsPing fires the equivalent for you.

   The snippet we’ll paste later in step 4 is AdsPing’s bridge to Google’s Conversions API, not Google’s own client-side tag. Click Done on this screen and exit the wizard.

8. 1.8 — Copy the Conversion Action ID

   Back on the Conversions list, you should see your new Purchase action with status Inactive — No recent conversions (this is expected; it’ll go active the first time AdsPing fires an event to it). Click the action name to open its detail page.

   Now look at the URL bar of your browser. It will look like this:

   https://ads.google.com/aw/conversions/customers/3884688380/detail?ctId=987654321

   The number after ctId= is your Conversion Action ID (in this example, 987654321). Copy it — you’ll paste it into AdsPing in step 2.

   The number after customers/ is your Customer ID. You don’t need to copy this — AdsPing pulls it automatically from your OAuth connection.

2. Wire the action in AdsPing

Now we tell AdsPing “forward Purchase events from this pixel to that conversion action”.

1. 2.1 — Open your pixel in AdsPing → Destinations tab → click Add action on the Google Ads card.
2. 2.2 — Fill the form:
   • Name: “Purchase — [your store]”
   • Customer: pre-filled from OAuth (Step 3 of the wizard).
   • Conversion action: pick the Purchase action you created in step 1 — the dropdown lists every ENABLED action from your account.
   • Event name filter: Purchase — this matches the event name we’ll fire from your site in step 4.
3. 2.3 — Save. The Google Ads card now shows the action with a green badge. See wizard Step 3 for screenshots of this dialog.

3. Copy the snippet

Pick one of the two formats below — whichever matches how you build your site. They both end up the same way on Google Ads.

<!-- Place inside the <body> of your order-confirmation /
     thank-you page, AFTER the AdsPing script in <head>. -->
<script>
  pbq('track', 'Purchase', {
    content_ids: ['SKU-1043'],
    content_type: 'product',
    num_items: 1,
    value: 199.90,
    currency: 'USD',
    order_id: 'ORDER-9381'   // important: enables cross-channel dedup
  });
</script>

<!-- Place inside the <body> of your order-confirmation /
     thank-you page, AFTER the AdsPing script in <head>. -->
<script>
  window.dataLayer = window.dataLayer || [];
  window.dataLayer.push({
    event: 'purchase',
    ecommerce: {
      transaction_id: 'ORDER-9381',
      value: 199.90,
      currency: 'USD',
      items: [
        { item_id: 'SKU-1043', item_name: 'Acme Hydrating Serum', quantity: 1, price: 199.90 }
      ]
    }
  });
</script>

4. Where to paste the snippet

Paste it inside the <body> of your order-confirmation page (the page customers see after a successful order). It must run AFTER the AdsPing script you added in Step 2 of the wizard — placing it anywhere in <body> guarantees that.

5. Test it

Complete a test order on your site (a free product, a discounted order, whatever your platform allows). After reaching the thank-you page, open your AdsPing dashboard and look at Recent Events for this pixel. A new Purchase row should appear within 10 seconds with a green Success badge.

Google Ads itself takes 3–24 hours to reflect new conversions in its UI. Check Tools → Conversions → your action → Recent conversions the next day.