ProPush.me Constructor is easy to set up and integrate, but it doesn’t mean you can launch it and let go. Like any others, your Constructor campaigns need to be carefully tracked – otherwise, you'll know you're getting traffic, but not where it's coming from or what's generating the best results.
Which source is converting? Which one is wasting your spending? Are the clicks real?
To answer these questions, you need an advanced tracker. And, you definitely want it to be easily integrated into your Constructor workflow, so meet Binom – your tool for tracking and optimization with an anti-fraud layer.
Constructor funnels have more variable parts than a standard landing page redirect. Look:
Each of those revenue streams generates a different signal, and you need to tie them to a specific source or zone. Without this breakdown, you won’t be able to blacklist the underperformers and scale what's working.
Binom is a self-hosted tracker built for affiliates running real traffic volume. Self-hosted means your data stays on your own server, not in a third-party cloud, which matters for both privacy and speed.
This tracker is built for performance: redirect times are fast enough not to affect conversion rates, and one license covers unlimited campaigns, traffic sources, and offers.
Briefly, it works like this:
You can break results down by zone ID, subzone, carrier, operating system, or other variables you need. And, you don't need a separate server for the landing page or a manual redirect chain between your tracker and your ProPush.me funnel.
Binom Protect is an optional add-on, and here is how it can help:
Why does this matter specifically for ProPush.me funnels? Because bot traffic doesn't subscribe to push notifications. If bots are clicking through your funnel, your push subscription rate looks lower than it actually is for real users, your zone-level performance data is skewed, and any optimization decisions you make on that data are responding to noise. Cleaning the data at the click level makes every downstream metric more reliable.
The detection system is modular. Binom Protect offers three presets:
Before you start filtering, Research Mode lets you run the detection without blocking anything. You see what was filtered, check that the detection is accurate for your specific traffic, and then turn blocking on when you're confident in the settings.
Tip: Start with Research Mode and Medium protection for 24 to 48 hours, review what gets flagged and why, and then adjust. The Paranoid preset can filter up to 25% of mobile traffic in some GEOs, so testing first is worth the extra step.
The integration runs in five steps. Here's the full flow.
Step 1: Download your landing page. In your ProPush.me personal account, configure your landing page and download the ZIP archive. Before downloading, make sure your APP_CONFIG is set correctly – zones, redirect logic, and domain settings all live there and need to be correct before you upload to Binom.
Step 2: Upload to Binom. Log in to your Binom admin panel, navigate to Landers, and click Create. Give the landing page a descriptive name. In the URL field, select the "No-redirect" option, then upload your ZIP archive. Binom unpacks and hosts the page. After upload, it assigns a path to your lander, typically starting with landers/.
Step 3: Set up a campaign. In Binom's Campaigns section, create a new campaign. Add your lander via the "+ Lander" button. You'll also need to create an offer – any placeholder URL works, because your APP_CONFIG zones handle the actual redirect logic rather than Binom's offer link. One important note: if your landing page can send multiple postbacks for the same click_id (common in upsell flows where a subscriber then converts on an offer), enable the Upsell checkbox in the offer settings. This tells Binom to sum payouts per click rather than overwrite the first one.
Step 4: Add tracking parameters to your campaign URL. Before sending any traffic, append the Binom-provided tracking parameters. The format looks like this:
https://{your_domain}/32ijo?var_1=${SUBID}&var_2={zone_id}&var_3={var_3}
The variables var_1, var_2, and var_3 carry your traffic source macros through to the ProPush landing page and on to redirects. How these maps work inside ProPush.me is covered in the URL parameters guide. Make sure Binom's macro placeholders match what your traffic source actually passes – a mismatch here is the most common reason tracking data doesn't show up in reports.
Step 5 (Optional): Enable the back feature. If you want Binom to log back and exit events from your landing page, open the lander code editor inside Binom (the <> button on the Landers page), find your APP_CONFIG block, and add:
back_pageUrl: 'https://{your_current_domain}/landers/{your_land_name}/back.html'
Replace the placeholders with your actual Binom campaign domain and the landing page name you used during upload. Once saved, back events will fire and appear in your Binom reports alongside subscriptions and conversions.
The full setup is documented at docs-const.propush.me/binom. If you run into a blank page after upload, the two most common culprits are index.html not being in the root of the ZIP archive and APP_CONFIG missing a required field. Check those first before anything else.
Pro tip: If your landing page sends multiple postback events (subscription + upsell conversion), set up the Upsell option in Binom before you start sending traffic. Fixing the payout logic retroactively means reconciling historical data, which takes longer than getting it right on day one.
Binom's tracker license is $149 per month. Binom Protect is an additional $99 per month, and one Protect license covers all your Binom tracker instances. If you're running more than one instance, the per-instance cost drops as you add them.
To start the integration with the ProPush.me partnership, sign up at binom.org/signup?from=PROPUSH. For documentation beyond the setup steps above, the Binom official docs cover campaign paths, postback configuration, and offer settings in detail.
