1) Install the Chrome extension

1. Open the Chrome Web Store listing: https://chromewebstore.google.com/detail/dr-utm-data-bridge/liefodheigfoplkgifknkidkgihbfnhc
2. Click Add to Chrome → Add extension.

2) Get your API Key (required)

The extension requires an API Key to fetch and display data.

• Request your API Key from the Dr. UTM Customer Success team.
• Once received, enter the API Key in the extension when prompted (or via the extension’s settings page, depending on your deployment).

If you do not have an API Key, the extension will not be able to retrieve or display metrics.

3) Where the extension works (Meta Ads Manager)

The extension injects a UTM metrics table directly into Meta Ads Manager views.

It detects the current table “level”:

• Ads level: supported
• Campaigns level: supported
• Ad Sets level: not supported yet 

4) When the injected table may not appear

The script suppresses the injected table if there isn’t enough horizontal space:

• There is a minimum width requirement.
• If the table area is too narrow, you will see a hint like: “Expand the Ad Name column to let UTM data fit in it.”
• Fix: drag to expand the “Ad Name” column (or widen the table layout) until the table has enough space.

5) Data refresh behavior (what triggers new data)

The extension refreshes/updates data based on:

• Date range changes in Meta Ads Manager (it reads the active date range from the UI and automatically refetches)
• Switching levels (Ads ↔ Campaigns)
• A Refresh Table Data button click (if present in your UI)
• Pagination (Next/Previous page)
• Scroll (re-renders visible rows and fills values from stored data)

Metrics shown in the injected table

These are the columns defined in dataArray:

SALES

• Meaning: Number of purchases.
• Source field: total_purchases
• UI behavior: If SALES > 0, the value becomes clickable and opens Sales Conversion Details.

COST PER SALE

• Formula: total_spend / total_purchases
• Shown as: currency (e.g., $12.34)
• If SALES = 0, shows $0.00.

LEADS

• Meaning: Number of leads.
• Source field: total_leads

COST PER LEAD

• Formula: total_spend / total_leads
• Shown as: currency

TOTAL REVENUE

• Meaning: Total purchase value (revenue).
• Source field: total_purchase_values
• Shown as: currency

PROFIT

• Formula: total_purchase_values - total_spend
• Shown as: currency Note: the UI removes the negative sign for negative profit and relies on red coloring to indicate negative values.

ROAS

• Formula: total_purchase_values / total_spend
• Shown as: a multiplier (e.g., 2.15x)

APPLICATIONS

• Meaning: Number of applications.
• Source field: total_applications
• UI behavior: If > 0, clickable and opens Application Conversion Details (event name used: SubmitApplication).

COST PER APPLICATION

• Formula: total_spend / total_applications
• Shown as: currency

SCHEDULES

• Meaning: Number of scheduled events/appointments.
• Source field: total_schedules
• UI behavior: If > 0, clickable and opens Schedule Conversion Details (event name used: Schedule).

COST PER SCHEDULE

• Formula: total_spend / total_schedules
• Shown as: currency

Click-through “Conversion Details” overlays (what users see)

When a user clicks SALES, APPLICATIONS, or SCHEDULES (only when the value is > 0), the extension opens a details overlay with a table containing:

• Date
• Email
• Name
• IP
• URL
• User Agent

The overlay supports pagination (10 rows per page in the UI logic).

Totals row (how totals are calculated)

The extension updates the last row in the table to display TOTAL values.

Totals are calculated from stored UTM data and:

• Filtered to the current Meta account_id (when it can be extracted from the page)
• Only includes rows where object_id is present (not null/empty)

Totals logic:

• SALES / LEADS / APPLICATIONS / SCHEDULES: summed
• TOTAL REVENUE: summed
• PROFIT: summed as (revenue - spend) per item
• COST PER *: computed as totalSpend / totalCount (overall blended CPA style)
• ROAS: totalRevenue / totalSpend