Tracking & Events

Tracking & Events is where you manage the sources that report customer activity and define the outcomes you want to measure.

• A data source (pixel or dataset) is where activity comes from.
• An event records an action, such as Subscribe or Purchase.
• A custom conversion combines a source, an event and matching rules to identify an outcome that matters to your business.

For related setup tasks, read Monitor landing pages with HeartBeat and Connect your Meta account.

What’s on the page

Tab	Use it to
Overview	See configured sources, custom conversions, connected platforms and events in the last 7 days
Pixels	Inspect one source: its events, diagnostics, history, pixel code and Conversions API setup
Custom Events	Create and manage custom conversions

Server Events is marked Soon and isn’t available yet.

Note: Configuration counts don’t prove events are arriving. A source marked Receiving with last activity weeks ago still needs checking. Look at recent event history.

Add a pixel

In Pixels, click New pixel. Before creating a new one, check whether your business already has a pixel you can reuse.

Create a new dataset

1. Choose Create new.
2. Enter a Dataset name that says what it’s for, for example Newsletter Subscribers.
3. Under Create dataset under, choose Business Manager to share it across ad accounts. (Ad Account is unavailable if the account already has a pixel.)
4. Optionally add a Website URL and Applicable categories.
5. Click Create dataset.

Creating a dataset doesn’t install tracking on your website. Copy the code from Pixel code and give it to whoever manages your site.

Connect an existing pixel

1. Choose Connect existing.
2. Select the pixel from the list. Check both the name and the ID, since similar names aren’t interchangeable.
3. Click Connect pixel, then check its activity.

Check that events are arriving

Select a source and confirm its name and Dataset ID before you change anything.

1. Pick a date range

Choose Today, 7 days, 14 days or 30 days. Use a short range after a site change, a longer one to find older activity.

2. Open History

Review the events received. An empty state means no events in that period, not necessarily no customer activity. Check the source and its implementation.

3. Run Diagnostics

Open Diagnostics for issues that affect matching or attribution, and click Refresh after fixing something. No issues found doesn’t prove every action you care about is being recorded.

Repeat this after a site release, a tracking change, or an unexpected drop in results.

Connect Conversions API

Conversions API sends server events through YieldBI while the browser pixel stays on your website.

1. Start setup

Select the source, open the Conversions API tab, check the source name and dataset ID, and click Connect Conversions API.

2. Generate a token in Meta

Click Open this dataset in Meta Events Manager, confirm the ID, then go to Settings → Conversions API → Generate access token. Click Next when you have it. YieldBI stores the token encrypted and won’t show it again.

3. Verify and connect

Paste the token into CAPI access token, check the dataset ID, tick the data-sharing confirmation if it’s accurate for your account, and click Verify & connect.

Check the resulting connection and event delivery before you treat setup as complete.

Define a custom conversion

Use a custom conversion to single out a specific action or destination within an existing source. You don’t need a new dataset for each conversion.

Goal	Example	Confirm that…
Grow a mailing list	Newsletter subscriptions	The event fires on a completed signup
Measure promotion interest	Signups for a specific offer	Source, event and URL rules match that offer
Track product consideration	Add to cart or wishlist	The event is the action, not just a page view
Track enquiries	Completed contact form	Submission is distinguished from opening the page

1. Open Custom Events

Click Add conversion. Use the Pixel filter to narrow the list if you manage several sources.

2. Name it and choose the source and event

Give it a purpose-led Conversion Name, select the Pixel / Data Source and the Standard Event (for example, Subscribe).

3. Add URL rules

Click Add URL condition, choose an operator and enter the URL. All rules must match. Avoid broad matches that catch unrelated pages.

4. Describe it and set a value (optional)

Add a Description so teammates can tell similar conversions apart. Set a Conversion Value only if it has a defined business meaning; leave it blank to use the pixel’s event value.

5. Create and verify

Click Create Conversion. New conversions show Inactive with no Last fired time until activity is recorded. Complete the action yourself, then check the event history and conversion list.

Warning: A signup-page URL doesn’t prove a signup happened. Make sure the event fires on the completed action, and that your URL rule matches where it fires, such as the confirmation page.