Trimrly Help Center

If you're running ads on X (formerly Twitter), you need the pixel working before you spend a significant budget. Without it, your X Ads account only sees impressions and clicks. It has no idea whether those clicks turned into signups, downloads, purchases, or any other action that actually matters to your business. The moment you add the pixel, that gap closes.

Connecting your X (Twitter) Pixel to Trimrly means every visit to a short link redirect page, bio page, or QR code landing page gets reported back to your X Ads Events Manager. Your retargeting audiences start building, your conversion data starts flowing, and X's algorithm gets the signals it needs to find more people like the ones who actually convert.

Your Twitter Pixel ID is a unique numeric string that looks like this: 123456789

What Is the X (Twitter) Pixel?

The X Pixel, also called the Twitter Website Tag, is a piece of JavaScript that loads on your web pages and tracks visitor behavior tied to your X ad campaigns. When a user clicks or views one of your ads and then lands on a page where the pixel is active, X matches that visit to their ad account and logs it as an interaction. If they then complete a defined conversion action, that event gets credited back to the relevant campaign, ad group, or creative.

It works similarly to the Meta Pixel or Google Ads conversion tag, but it's specifically tied to activity on X. The platform handles attribution across clicks, replies, retweets, favorites, and even impressions, so you get a fuller picture of how your ads are influencing behavior than pure click-based tracking alone would give you.

There are two components to how X tracking works:

The Base Pixel (Website Tag)

This is the foundational script that loads on every page. It fires a PageView event automatically on each page visit, identifies the X user if a cookie is present, and starts building your website audience in the background. You only need one base pixel per website, identified by a single numeric Pixel ID. This is what you'll connect to Trimrly.

Conversion Events

On top of the base pixel, you can define specific actions as conversion events inside X Events Manager. Each event gets its own event ID (starting with tw-) that fires only when a particular condition is met, like a form submission page loading or a purchase completing. These give you granular conversion data beyond the page view level.

What Conversion Types Can You Track?

X supports a range of standard conversion event categories that map to common business goals. Here are the ones most relevant to Trimrly campaigns:

• Site Visit. Fires when a user lands on a specific page after engaging with your ad. This is the most basic conversion and fires automatically through the base pixel on your Trimrly redirect pages.
• Sign Up. Tracks when a user registers for a service, newsletter, or account. Useful if your Trimrly short links drive traffic to a registration page and you want to count completed signups rather than just visits.
• Lead. Previously called Sign Up in some X Ads interfaces. Fires when a user submits contact information, fills out a lead form, or takes an action that qualifies them as a lead in your funnel.
• Purchase. Tracks completed transactions and can pass order value data back to X Ads. This is the event X's algorithm uses most aggressively to optimize delivery toward users with buying intent.
• Download. Fires when a user downloads a file, whitepaper, app, or other asset from your destination page. Good for content marketing campaigns where the conversion goal is asset access rather than a form fill.
• Content View. Tracks visits to key pages like product pages, service pages, or pricing pages. Helps build high-intent retargeting audiences from people who got close to converting but didn't complete the action.
• Custom. A catch-all category for any conversion action that doesn't fit the standard event types. You define the trigger logic yourself, giving you flexibility for niche use cases specific to your product or campaign structure.

How to Find Your X (Twitter) Pixel ID

Your Pixel ID is the unique numeric identifier for your website tag inside X Ads. Here's where to find it:

1. Log in to your X Ads account at ads.x.com.
2. Click Tools in the top navigation menu.
3. Select Events Manager from the dropdown.
4. If you haven't created a pixel yet, click Add Event Source and choose Website Tag. Follow the prompts to generate one.
5. If you already have a website tag set up, click on it to open the details. Your Pixel ID is the numeric string displayed in the tag overview, for example 123456789.
6. Copy that number. It's what you'll paste into Trimrly.

Note that the Pixel ID and the event IDs for specific conversion events are different things. The Pixel ID identifies your base website tag. Event IDs (which start with tw-) identify individual conversion actions. For the Trimrly connection, you need the base Pixel ID only.

How to Add Twitter Pixel to Trimrly

Once you have your Pixel ID ready, adding it to Trimrly takes about two minutes through the Tracking Pixels section:

1. Log in to your Trimrly account. No account yet? Create a free account here.
2. In the left sidebar, click Tracking Pixels under the Channels section.
3. On the Add Pixel page, open the Pixel Provider dropdown and select Twitter.
4. In the Pixel Name field, enter a descriptive label, such as "X Ads Pixel" or the name of your active campaign.
5. Paste your numeric Pixel ID (for example 123456789) into the Pixel Tag field. Do not paste the full JavaScript code snippet, just the number.
6. Click Add Pixel to save.

Once saved, Trimrly loads your X base pixel on all short link redirect pages, bio pages, and QR code landing pages. Every visit to those pages fires a PageView event back to your X Ads Events Manager.

Setting Up Conversion Events in X Events Manager

The base pixel handles page view tracking automatically. But if you want to count specific actions like signups, purchases, or downloads as conversions, you need to define those inside X Events Manager as well.

Here's how to create a conversion event:

1. In X Ads Manager, go to Tools > Events Manager.
2. Click Add Event and choose a conversion type from the list (Site Visit, Sign Up, Purchase, Download, etc.).
3. Name the event clearly so you can identify it in reports, for example "Bio Page Signup" or "QR Code Landing Visit."
4. For URL-based conversions, set the trigger to fire when a specific URL loads, like a page containing "/thank-you" or "/confirmation."
5. X will generate a unique event ID starting with tw-. This ID is what you'd reference if you later want to track this event through Google Tag Manager rather than as a URL-based trigger.

One important note from X's own documentation: avoid creating multiple conversion events of the same type. For example, if you have two "Purchase" events set up, you split the conversion signal and weaken the algorithm's ability to optimize. One well-configured event per conversion type is the right approach.

How to Verify Your X Pixel Is Working

Take a few minutes to confirm the pixel is firing before you launch a live campaign. Catching a problem now costs nothing. Catching it after a week of ad spend is a lot more painful.

Install the Twitter Pixel Helper Chrome extension (search for it in the Chrome Web Store). Once it's active, visit one of your Trimrly short link redirect pages or bio pages. The extension shows whether the pixel loaded, what Pixel ID was detected, and whether any events fired. If the Pixel ID it shows matches what you entered in Trimrly, you're good.

For a secondary check, go back to Events Manager inside X Ads and look at the recent activity for your website tag. If the tag is receiving signal, you'll see page view activity in the event history. X can take a few hours to process and display this data, so don't worry if it's not instant.

Important Notes Before You Start

• Enter the numeric Pixel ID only. Trimrly handles the script wrapper. All you need in the Pixel Tag field is the number itself, like 123456789. Pasting the full JavaScript snippet will cause the integration to fail.
• Double-check every digit. The Pixel ID is a numeric string with no tolerance for typos. One wrong digit means no data reaches X Ads. Copy it directly from Events Manager rather than typing it by hand.
• Allow a few hours for data to appear. X Ads doesn't display conversion data in real time. After saving in Trimrly and visiting your pages, give Events Manager a few hours before checking for activity. Some data points can take up to 24 hours to fully process.
• Avoid duplicate pixel installs. If you're also managing the X pixel through Google Tag Manager connected to Trimrly, don't add a second instance through the standalone Twitter pixel slot on the same pages. Duplicate base pixels inflate your audience data and can confuse attribution reporting.
• Don't create multiple events of the same type. X's own guidance is clear here: splitting your Purchase or Sign Up events across multiple event configurations dilutes the conversion signal and makes it harder for the algorithm to optimize. Consolidate into one event per conversion category.
• Privacy compliance still applies. In GDPR-covered regions or other markets with consent requirements, make sure the X pixel is gated behind your cookie consent banner before firing. Running the pixel on visitors who haven't consented creates legal risk regardless of where the tag is hosted.

Why Connect X (Twitter) Pixel with Trimrly?

X is a platform where real-time content travels fast. Short links are a natural fit for the format. A well-crafted tweet with a Trimrly short URL is clean, branded, and trackable. But without the pixel on the other side of that click, you're only measuring reach, not results.

With the X pixel active on your Trimrly pages, every campaign touchpoint produces usable data. Someone clicks a Promoted Tweet linked to your short URL? The base pixel fires on the redirect page. They land on your bio page from your X profile link? Same thing. They scan a QR code that leads to a Trimrly redirect? That visit gets tracked too.

Here's what that data gets you in practice:

• Real conversion numbers, not just click counts. You can stop optimizing for clicks and start optimizing for the actions that actually matter to your business, whether that's signups, downloads, or purchases.
• Retargeting audiences built automatically. Everyone who visits your Trimrly pages gets added to your X website audience. You can retarget them with follow-up ads, suppress them from acquisition campaigns once they've converted, or use them as a seed for lookalike targeting.
• Better algorithm optimization. X's campaign delivery algorithm uses your conversion events to find more users who look like your converters. The more signal it gets, the more efficiently it spends your budget. Running without conversion data leaves that optimization entirely off the table.
• Attribution across engagement types. X tracks conversions tied to clicks, but also to views, retweets, and other engagement types within the attribution window. This gives you a fuller picture of how your organic and paid X activity work together than click-only tracking would provide.
• Cleaner campaign decisions. When you can see which specific campaigns and creatives are generating the most conversions through your Trimrly links, scaling what works and cutting what doesn't becomes straightforward rather than guesswork.

Questions about the setup? The Trimrly team is happy to help. Reach out here and we'll get you sorted.

Read the official X (Twitter) conversion tracking guide