The Basic Architecture
Retargeting landing page visitors requires three pieces:
- Meta Pixel installed on your landing page to track browser-side visits
- Conversions API (CAPI) sending server-side events for reliability
- Custom Audiences built from that tracking data
The pixel alone is not enough in 2026. Ad blockers, Safari's Intelligent Tracking Prevention, and iOS App Tracking Transparency all reduce browser-side tracking accuracy. CAPI fills the gaps by sending events directly from your server to Meta.
Meta recommends dual tracking: pixel plus CAPI with deduplication. This setup gives you the most complete picture of who visited and what they did.
Step 1: Install the Meta Pixel
The Meta Pixel is a JavaScript snippet that goes in the <head> section of your landing page. It fires a PageView event every time someone loads the page.
Create or access your pixel in Events Manager Go to Meta Events Manager, select your ad account, and either create a new pixel or use an existing one. Copy the base code snippet.
Add the pixel to your landing page Paste the base code in the
<head>section of your landing page. If you use a landing page builder like Linkfire, FeatureFM, or Toneden, paste your Pixel ID into the platform's integration settings.Verify the pixel is firing Install the Meta Pixel Helper Chrome extension. Visit your landing page. If the extension icon turns blue and shows events, the pixel is working. If it stays grey, check your installation.
The base pixel tracks PageView automatically. For music campaigns, you should also track intent events like Lead (when someone submits their email) or a custom event like SaveIntent (when someone clicks to save on Spotify).
Step 2: Set Up Conversions API
Browser tracking undercounts. CAPI sends the same events from your server, bypassing ad blockers and browser restrictions.
You have three options for setting up CAPI:
Partner integration. If you use Shopify, WordPress, or a major landing page platform, check for a native CAPI integration. This is the fastest path.
CAPI Gateway. Meta's no-code solution that runs through AWS. You configure it in Events Manager without writing code, but it requires some setup time.
Manual implementation. Your developers send events directly to Meta's API. This gives the most control but requires engineering resources.
For music campaigns using landing page services like FeatureFM or Linkfire, check if the platform supports CAPI natively. Many now do.
Note Deduplication matters. Both pixel and CAPI may fire for the same event. Use a shared
event_idparameter so Meta counts it once, not twice.
Step 3: Create Custom Audiences
Once tracking is live, you can build audiences from your landing page visitors.
Go to Audiences in Ads Manager From Meta Ads Manager, click on Audiences in the left menu, then click Create Audience and select Custom Audience.
Choose Website as the source Select your pixel from the dropdown. This pulls from both pixel and CAPI events.
Define your audience rules The simplest rule is "All website visitors" with a retention window. You can also filter by specific URLs (only people who visited your landing page, not your whole site) or by events (only people who triggered
SaveIntent).Set the retention window This is the rolling lookback period. People stay in the audience for this many days after their last qualifying visit, then drop out.
Use descriptive names like LandingPage_Visitors_30Days or SaveIntent_NotCompleted_14Days. You will build multiple audiences with different windows, and clear naming prevents confusion.
Retention Windows for Music
Music retargeting windows should be longer than ecommerce. Someone buying shoes decides in hours. Someone becoming a fan decides over weeks.
| Window | Use case |
|---|---|
| 7 days | Hot leads for release week pushes |
| 14 days | Standard retargeting for active campaigns |
| 30 days | Broad retargeting for ongoing catalog promotion |
| 60-90 days | Tour or album cycle audiences |
| 180 days | Maximum window for reactivation campaigns |
The tradeoff is relevance versus volume. A 7-day window is highly relevant but small. A 180-day window is large but includes people who may have forgotten why they clicked.
For most music campaigns, 14-30 days is the default. Extend to 60-90 days if you are building toward a major release and want to warm up everyone who engaged in the past quarter.
Tip Create overlapping audiences at multiple windows (7, 14, 30, 60 days) from the same pixel events. This lets you test which window converts best for your specific campaign.
Audience Segmentation
Not all landing page visitors are equal. Segment by behavior to match your messaging.
Visitors who did not take any action. These are your largest pool. They clicked, looked, and left. Retarget them with reminder creative that reinforces the hook.
Visitors who started but did not complete. If someone clicked "Save on Spotify" but did not finish, they showed clear intent. Retarget them with a nudge, not a re-pitch.
Visitors who completed an action. These people already saved or followed. Exclude them from save-focused retargeting. Show them depth content instead: behind-the-scenes, upcoming releases, or tour announcements.
To build these segments, track granular events. A landing page that only fires PageView cannot distinguish between bounce and intent. Add events for SaveIntent, SaveCompleted, Lead, or whatever actions matter.
Creative Sequencing
Retargeting is a narrative, not a repeat blast. Each ad in the sequence should build on the previous one.
Ad 1: Reminder. Same song, different angle. Reinforce the hook they already heard. Use the same visual language so they recognize the artist.
Ad 2: Proof. Show that other people love this song. Creator clips, user-generated content, playlist placements, or streaming milestones. Social proof works because it resolves uncertainty.
Ad 3: Depth. Give them more of the artist. A longer performance, a lyric video, a personal story. This is where you build relationship, not just recall.
The sequence depends on your audience size and campaign budget. If your retargeting pool is small (under 1,000 people), you may only run one ad. If it is large, you can layer multiple ads with frequency caps.
Warning Watch your frequency. If the same person sees your retargeting ad more than 3 times without converting, either refresh the creative or accept that they are not going to convert. Overexposure burns goodwill.
Excluding Converters
Once someone completes your goal action, stop showing them the same ad. This is both a cost saver and a user experience win.
Create an exclusion audience:
- Source: Website
- Event:
SaveCompleted(or your equivalent) - Window: Same as your retargeting window or longer
Apply this exclusion at the ad set level. People in the exclusion audience will not see your retargeting ads.
If you want to keep them in a nurture sequence, move them to a different campaign with different creative. Show them tour dates, merch, or the next single instead of the same save CTA.
Lookalike Audiences from Converters
Once you have enough conversions (Meta recommends 100+), you can build lookalike audiences from your most valuable visitors.
Create a source audience of people who completed a high-intent action, like saving the song or joining your email list. Then create a 1% lookalike in your target countries. This audience shares behavioral patterns with your converters but has not been exposed yet.
Lookalikes are for prospecting, not retargeting. Use them to find new cold audiences that resemble your best warm leads.
CAPI Integration Deep Dive
For teams doing manual CAPI implementation, here are the key requirements:
Events to send: At minimum, send PageView, ViewContent, and your primary conversion event. For music, this is usually Lead (email capture) or a custom event like SaveCompleted.
Required parameters: Each event needs event_name, event_time, user_data (hashed email, phone, or both), and event_source_url.
Deduplication: Use the same event_id for browser and server events. Meta will deduplicate and count it once.
Event Match Quality (EMQ): Monitor this metric in Events Manager. It measures how well Meta can match your events to users. Higher EMQ means better optimization. To improve it, send more user data fields (email, phone, first name, last name, city, state, country, zip) in hashed form.
If your EMQ is below 6.0, troubleshoot your data matching. The most common issues are missing email addresses or improperly hashed fields.
Dynamoi and Retargeting
Dynamoi handles pixel installation, CAPI integration, and audience building as part of campaign setup. Custom audiences are created automatically from landing page events, and retargeting sequences are managed within the campaign structure.
For teams running their own campaigns, the principles above apply regardless of tooling. The mechanics of pixel, CAPI, and custom audiences are the same whether you use Dynamoi, Ads Manager directly, or another platform.