How ad networks are structured
PNLight uses three levels for paid acquisition setup:- Network: a provider such as Facebook or a custom traffic source.
- Account: a connected Facebook ad account or a custom account inside that network.
- Campaign: a synced or manual campaign that appears under the selected network or account.
Before you start
For a Facebook connection, prepare access in Meta before you add the account in PNLight.- You need admin access to the Meta business portfolio that owns the ad account.
- You need access to the ad account that runs the campaigns.
- You need a Meta dataset or pixel if you want PNLight to send events through Meta Conversions API.
- You need an app link or landing URL for click redirects.
PNLight uses the Marketing API token to sync campaigns and spend. PNLight uses the pixel token only when you enable Conversions API event delivery.
Connect a Facebook account
Enter Conversions API settings
Add Facebook Pixel ID (Conversions API) and Facebook Pixel Access Token (Conversions API) if you want PNLight to send events to Meta.
Set the default redirect URL
Add Redirect URL (default). PNLight sends users to this URL after it records the ad click.
Get the Facebook credentials
You need a Facebook ad account ID and a Marketing API access token to connect a Facebook account. Add the pixel ID and pixel access token only when you want PNLight to send mapped events to Meta Conversions API.Get the ad account ID
Get the Marketing API access token
Create a system user token for PNLight. Do not use a short-lived Graph API Explorer token.Open the business portfolio
Open Meta Business Settings and select the business portfolio that owns the ad account.
Create a system user for PNLight
Open Users > System users and click Add. Name the user
PNLight or another clear service name.Give the system user ad account access
Select the system user, click Add assets, choose Ad accounts, and select the ad account you will add to PNLight. Grant access that allows PNLight to read campaigns, ad sets, ads, and insights.
Choose the Meta app
Click Generate new token and select the Meta app that belongs to the same business portfolio. If you do not have an app yet, create one in Meta for Developers and connect it to this business portfolio.
Select Marketing API permissions
Select
ads_management. Select ads_read too if Meta shows it for your app.Get the pixel ID and pixel access token
Use these values only when you want PNLight to send mapped events to Meta Conversions API.Generate the access token
Open the Conversions API settings for the data source and generate an access token.
Add a custom network or account
Use a custom setup when the traffic source is not connected through Facebook sync.Add aliases
Add attribution aliases such as provider-specific names or normalized labels that PNLight should treat as the same network.
Configure network settings
Open a network from the table when you need to manage shared delivery settings. Use the network page to:- Rename the network.
- Update attribution network aliases.
- Define default system event postbacks.
- Define default app event postbacks.
- Map PNLight events to Facebook standard events when you use Facebook Conversions API.
Configure account settings
Open an account when you need account-specific click and delivery settings. Use the account page to:- Set or change the default redirect URL.
- Copy URL for your Ad for Facebook campaign destinations.
- Update Facebook access tokens.
- Update Facebook pixel credentials.
- Turn Send events to Facebook Conversions API on or off.
After setup
- Open Campaigns and sync or review the campaigns for that account.
- Use ad network and ad campaign filters across Analytics, Customers, and Events.
- Keep attribution aliases current when your provider sends a new network label.
- Turn on Conversions API only after the pixel credentials and event mapping are ready.
Use Campaigns after you connect an account to review enabled campaigns, costs, postbacks, and campaign metrics.