From checkout to tracked purchase

PingItNow connects Stripe and Whop checkout to a customizable thank-you page where your tracking scripts can run after a verified payment. Use your existing analytics, advertising, or attribution provider; PingItNow is not limited to Hyros and is not affiliated with the providers mentioned in this guide.

The usual journey is your website → Stripe or Whop checkout → your PingItNow thank-you page → optional next step. Keep your provider's tracking installed on your website to capture visits before checkout. The thank-you page supplies the purchase context that can connect a buyer to that earlier visit. Identity matching and final attribution depend on the provider, consent, browser restrictions, and your domain configuration.

This guide describes the current application. Screenshots labeled Demo show real application screens with simulated data; they do not represent live revenue or connected merchant accounts.

Get started and explore the demo

1. Open PingItNow and use the site's sign-up option to create your account, or sign in to your existing account.
2. For a walkthrough before connecting accounts, open the interactive demo.
3. Navigate between the demo's dashboard, payment links, thank-you pages, transactions, domains, recovery, and settings screens.
4. The Demo: On indicator and Sample data · Demo mode banner identify simulated activity. Demo settings and transactions do not contact payment services or charge a customer.
5. Use the real dashboard to configure your own account. A connected status inside the demo does not connect your real Stripe or Whop business.

The interactive demo overview with its sample-data banner · Select to enlarge

Your first setup

Complete these steps in order:

1. Connect Stripe or Whop in Settings → Integrations.
2. Optionally add and verify a domain in Settings → Domains.
3. Save a supported script in Settings → Tracking.
4. Create or import a payment link and select its thank-you-page domain and template.
5. Open its checkout using View Link → and verify a payment in a suitable test environment.
6. Check Attribution diagnostics, then confirm the purchase in your tracking provider.

Connect Stripe

1. Open Settings → Integrations and select Stripe.
2. Click Connect with Stripe.
3. Sign in on Stripe's authorization page and select the merchant account you intend to use.
4. Review Stripe's requested access and authorize the connection.
5. Return to PingItNow. The integration should show Account Connected and the connected account identifier.
6. Open Payment Links to create a new link or explicitly import existing links.

Stripe uses OAuth. You do not enter your Stripe password into PingItNow. Connecting an account alone is not proof that every existing link redirects correctly; review the links you create or import and their synchronization status.

Settings integration list showing where to open Stripe · Select to enlarge

The integration list identifies the Stripe entry. Open that entry to access its connection controls; this capture does not show the OAuth authorization flow.

If the panel shows Connection Expired, click Reconnect with Stripe, authorize the correct merchant account again, and review Attribution diagnostics → Checkout redirect synchronization. Avoid distributing a link while its redirect synchronization reports an error.

Connect Whop

Whop requires a Company API Key and a Webhook Signing Secret from the same business. Use the business that owns the plans you want to sell.

1. In Whop, open that business's Developer dashboard. The generic developer link may require selecting a business first.
2. Create a Company API Key. If Whop offers inherited or custom permissions, choose the permissions needed for your intended actions.
3. Enable the permissions listed in PingItNow's setup panel:

The checkout permission is necessary to generate a checkout with the return URL configured. Member email access is necessary when buyer identity must be retrieved from Whop. Read-only permissions can make the connection appear usable while checkout creation still fails.

4. In PingItNow, open Settings → Integrations → Whop and paste the key into API Key.
5. Copy the exact webhook endpoint shown by PingItNow's Configure Webhook section. Use the endpoint for the environment you are configuring; production and QA are different destinations.
6. In the same Whop business, create a webhook for that endpoint and select payment_succeeded and membership_activated in the dashboard event picker. Whop's picker uses underscores, while delivered webhook payloads use the corresponding dotted event types, payment.succeeded and membership.activated, handled by PingItNow. These are two naming formats for the same events; do not change the payload format. Whop's official integration guide explains the dashboard-versus-payload naming distinction.
7. Copy its signing secret into Webhook Signing Secret in PingItNow.
8. Click Connect Whop.
9. Confirm Account Connected and Webhook configured, then test an actual checkout flow.

The Whop entry appears in the same Settings → Integrations list shown above. Open it to access the API-key and webhook setup fields. The screenshot shows navigation, not the credential setup form.

Use Update next to the webhook secret field when rotating the secret. Update the value to match Whop's current webhook configuration. Never put API keys or webhook secrets into screenshots, public documentation, payment URLs, or tracking snippets.

For an imported Whop plan, distribute the View Link → provided by PingItNow. An unrelated original Whop plan URL may not carry PingItNow's checkout redirect configuration.

Add a custom domain

A custom domain makes the thank-you page part of your own brand. When a provider uses first-party cookies, a suitable domain can help it recognize visitors from your website. A domain alone does not guarantee identity continuity; check your provider's cookie and tracking configuration.

1. Open Settings → Domains.
2. Click Add Domain.
3. Enter a hostname, such as pay.example.com, in Domain Name. Enter the hostname without https://, a path, or query parameters.
4. Click Add Domain.
5. At the DNS provider for example.com, add the CNAME record displayed by PingItNow. For the example above, the application currently displays:

6. Allow DNS changes to propagate, then click the domain's Verify domain action.
7. Wait for Verified before selecting the domain for a live payment link.

Add Custom Domain form with an empty hostname field · Select to enlarge

Enter the hostname you own; the placeholder is an example, not a configured domain.

Custom domains in Demo mode with simulated verification · Select to enlarge

Demo illustration: the sample domain controls simulate verification and do not change DNS. Follow the Settings → Domains instructions above for your real domain.

Use a subdomain if your DNS provider does not support CNAME records at the root. Follow any additional ownership verification requirement returned by the hosting service; contact support if the app does not display enough information to finish verification.

Domain settings

Click Edit settings on the domain to configure its Domain-Specific Tracking Script and redirect behavior. Leave the tracking field empty to inherit the global tracking script from Settings → Tracking. Domain-level tracking overrides the global setting; it does not automatically append to it.

The domain card reports Tracking: Custom or Using Global, and Redirect: Using Global, a delay, or Disabled. Set as primary marks your preferred domain, but still check the domain selected on each payment link. Deleting a domain can affect links that use it; update those links first.

Configure tracking scripts

1. Obtain the official installation snippet from your analytics, advertising, or attribution provider.
2. Open Settings → Tracking.
3. Paste it into Tracking Scripts.
4. Click Save Changes.
5. Open Attribution diagnostics and click Check tracking scripts.
6. Verify a paid checkout and inspect the event in the provider's own dashboard.

Tracking settings with an illustrative unsaved configuration · Select to enlarge

The editor shows a generic example for illustration. Replace it with your provider's own valid identifier and save your configuration before testing.

What is supported

PingItNow's purpose is to run supported tracking integrations on the post-payment thank-you page, regardless of whether you use Hyros. Compatibility has three distinct levels:

The approved host list currently covers Google, Meta, TikTok, LinkedIn, X, Microsoft, Segment, HubSpot, Mixpanel, Hotjar, Amplitude, and Hyros. Being on this list does not imply a built-in purchase-event adapter for every provider. A Google Tag Manager container still needs the appropriate tags and triggers configured in Google; loading it does not create those settings for you.

Only supported <script> configurations are accepted. You can configure multiple supported script tags in the same field. Arbitrary inline JavaScript is not executed. Extra HTML, image tags, event handlers, unapproved hosts, and unsupported inline snippets are rejected. For example, omit the <noscript> image from a Meta installation snippet. Scripts are limited to 10,000 characters.

If your provider uses a custom hostname or needs its own purchase callback, ask support to verify compatibility before going live. Do not assume that loading the script alone sends your desired conversion event.

Copy-paste configuration examples

These examples use placeholder identifiers. Replace every example ID with the ID from your own provider account before saving. They are PingItNow configurations for the thank-you page, not installation instructions for arbitrary websites. You can place multiple supported tags in the same Tracking Scripts field.

Meta Pixel with automatic purchase dispatch: replace 123456789012345 with your numeric Pixel ID.

<script
  src="https://connect.facebook.net/en_US/fbevents.js"
  data-pingitnow-provider="meta"
  data-pixel-id="123456789012345"
></script>

PingItNow initializes that pixel and invokes its configured Purchase after payment verification and consent. Do not add a second manual purchase event for the same payment. Check the resulting event in Meta's event tools.

GA4 with automatic purchase dispatch: replace G-ABC1234567 in both locations with your GA4 Measurement ID.

<script
  src="https://www.googletagmanager.com/gtag/js?id=G-ABC1234567"
  data-pingitnow-provider="ga4"
  data-measurement-id="G-ABC1234567"
></script>

PingItNow configures that measurement ID and invokes purchase with the verified transaction ID, value, and currency. Confirm the event in GA4. Use the same measurement ID in the URL and the configuration attribute.

Google Tag Manager external container script: replace GTM-ABC1234 with your container ID.

<script src="https://www.googletagmanager.com/gtm.js?id=GTM-ABC1234"></script>

This loads an approved external script. It does not create your Google-side tags or triggers, run arbitrary inline container bootstrap code, or automatically emit a purchase data-layer event for the container. Configure and validate the container's own initialization and triggers with your tracking specialist. Prefer the GA4 configuration above when you need PingItNow's built-in GA4 purchase adapter.

Consent, buyer identity, and URL parameters

The thank-you page verifies the payment before using its buyer information. Tracking requires the visitor's tracking consent; declining consent prevents tracking dispatch. Preview and demo screens do not produce a real purchase event.

For the existing Hyros-compatible buyer identification flow, the verified buyer email is exposed as he in the thank-you-page URL after consent. The application does not add a duplicate email parameter. This is a provider-specific compatibility detail, not a requirement to use Hyros.

UTMs already present in the thank-you-page URL remain available. Do not assume Stripe forwards arbitrary custom checkout URL parameters such as fbc_id or h_ad_id. Keep your provider installed on the pages customers visit before checkout so it can capture the original visit. PingItNow does not currently add an intermediate click-tracking link or guarantee recovery of parameters a checkout provider discards.

Create a Stripe payment link

1. Open Payment Links and click + Create Payment Link.
2. If both payment providers are connected, select Stripe.
3. In Create Stripe Payment Link, enter Link Name. This is your internal label.
4. Choose a product and price from Existing Products, or choose + Create new product.
5. For a new product, enter Product Name, select One-Time or Recurring, and enter the price and currency. Product Name is shown to the customer.
6. For a recurring price, configure Billing Period and, if needed, Free Trial Period (Optional). A trial is not the same as an immediately paid purchase; test your intended conversion behavior.
7. Select Custom Domain: Shared (pingitnow.com) or a verified domain you own.
8. Select Thank You Template, and optionally fill TY Headline (Optional) and TY Message (Optional).
9. Review the optional checkout and advanced settings. Use tax and terms-of-service options only when the corresponding Stripe account configuration is ready.
10. Click Create.
11. Open View Link → on the created row to inspect checkout. Verify redirect synchronization and a complete purchase before sharing the link.

Stripe payment-link creation form · Select to enlarge

Stripe creation form: domain, thank-you template, optional text, and Create button · Select to enlarge

Choosing an existing price uses that price's billing behavior. Changing a PingItNow label or thank-you message does not change the underlying checkout price.

Create a Whop checkout link

1. Open Payment Links → + Create Payment Link and choose Whop, if prompted.
2. In Create Whop Checkout Link, enter the internal link name and the customer-facing title.
3. Under Plan Type, choose Free, One-Time, or Recurring, then complete the applicable amount, currency, and billing-period fields.
4. Select a verified Custom Domain, or use the shared domain.
5. Select Thank You Template and optionally customize the headline, message, and description.
6. Review the optional settings displayed by the form. Whop's custom checkout questions support text fields in this application.
7. Click Create Checkout Link.
8. Use that row's View Link → to open the checkout with PingItNow's return configuration.

Whop checkout creation form before saving · Select to enlarge

The form shows an unsaved configuration. Complete the fields for your own offer and create the checkout link before sharing it.

A free plan is not evidence of a paid conversion. Configure and test the behavior appropriate to your offer. If checkout reports a permissions error, enable checkout_configuration:create on the Company API Key for the same Whop business.

Import existing links and plans

Stripe

1. Open Payment Links → Import and select Stripe, if prompted.
2. Review Import Payment Links. Already imported links are excluded from the new-link list.
3. Check the links to import. Use the top checkbox to select or deselect the displayed list.
4. For each selected link, choose the shared domain or a verified custom domain for its Thank You Page URL.
5. Review the confirmation and import the selected links.
6. Return to Payment Links, inspect the links, and verify checkout redirect synchronization.

Importing configures the post-payment destination on the selected Stripe links. This can change where existing customers are sent after completing checkout; choose the destination deliberately.

Whop

1. Open Payment Links → Import and select Whop, if prompted.
2. Review Import Whop Plans and select the plans you want.
3. Choose a shared or verified custom thank-you-page domain for every selected plan.
4. Click Import … Selected Plan(s), review Confirm Import, and click Yes, Import.
5. Use the imported rows' View Link → when distributing your checkout URLs.

Import results can be partial. Read the reported imported and failed counts, fix the failed items, and retry only those items. Do not interpret a partial import as success for every selected plan.

Edit, rename, preview, and delete

Use a payment-link row's Edit button to change its internal name, domain, thank-you-page template, headline, or message. The application reports whether checkout synchronization succeeded or whether an update needs attention. Review synchronization errors in Attribution diagnostics.

Use the rename control for an internal label change. Click the thank-you-page URL or Preview TY Page to inspect its appearance. Preview mode disables tracking and automatic redirects; it does not prove a purchase event was sent.

Use Delete only after reviewing its confirmation and any option to archive on the payment platform. Removing a PingItNow record and archiving a provider's offer are different actions. Check the confirmation before affecting a live offer.

Payment-link list in the simulated demo · Select to enlarge

Customize your thank-you page

1. Open Thank You Pages to browse Thank You Page Templates.
2. Click Preview Template to inspect a design, then Back to Templates to return.
3. Select the template when creating or editing a payment link.
4. Set the link's optional headline and message to match your offer.
5. Preview that specific link's thank-you page from Payment Links.

Thank-you-page template library in Demo mode · Select to enlarge

A simulated thank-you-page preview in Demo mode · Select to enlarge

The template gallery currently provides system templates. A template preview is a design preview, not a confirmed transaction. Live checkout verifies the buyer and payment before displaying purchase data and dispatching tracking.

Configure the next-step redirect

1. Open Settings → Redirect.
2. Enable Enable automatic redirect after payment.
3. Set Wait Time (seconds) between 1 and 60.
4. Enter the full Redirect URL, such as https://example.com/welcome.
5. Click Save Changes.
6. If a domain has its own redirect setting, review Settings → Domains → Edit settings. It can inherit the global configuration or override it.

Redirect settings with an illustrative destination · Select to enlarge

The example destination is illustrative. Enter your own next-step URL and save it for your customers.

Allow enough time for the thank-you page and tracking process. The application coordinates the redirect with tracking readiness; a preview intentionally does not redirect. Verify the complete browser journey with the same consent behavior your customers will encounter.

Verify an end-to-end purchase

Use your payment provider's appropriate test environment before accepting real payments. The interactive demo does not replace this check, and a live checkout can charge a real card.

1. Visit your normal landing page with your tracking provider installed, using a recognizable test campaign if needed.
2. Open the payment link from PingItNow's View Link →.
3. Complete the checkout in the intended payment-provider environment.
4. Confirm that the browser lands on the correct thank-you-page domain and design.
5. Accept tracking consent if your test is intended to send a tracking event.
6. Open Attribution diagnostics in PingItNow. Check integration readiness, verified domains, checkout redirect synchronization, and recent purchase tracking.
7. Click Check tracking scripts to test saved-script availability without sending another buyer or purchase.
8. In your provider's own dashboard, verify the buyer identity when supported, transaction identifier, purchase value, currency, and campaign attribution.
9. Confirm the purchase appears in Transactions and that the payment platform delivered its webhook successfully.

Script available means the script endpoint passed the availability check. Dispatched means the browser loaded the integration and invoked its configured event. Neither is proof that the provider accepted the purchase or attributed it to the right campaign. The provider's event tools and dashboard are the final check.

Refreshing a paid thank-you page should not be used as a routine way to resend conversions. PingItNow includes duplicate protection; diagnose a missing conversion before attempting a replay.

Use the dashboard

Transactions screen in Demo mode with fictional customer data · Select to enlarge

Customer subscriptions screen in Demo mode with fictional customer data · Select to enlarge

Failed-payment recovery

Payment recovery helps existing subscription customers resolve failed payments; it is separate from attribution tracking.

1. Open Dunning & Recovery and its settings page.
2. Under Retry Schedule, set Maximum Retries.
3. Configure Retry Intervals (days after previous attempt). Use Add Retry Interval or the remove control to change the schedule.
4. Review Schedule Preview. The days accumulate from one retry to the next; they are not all measured independently from the original failure.
5. Under Email Notifications, choose Send dunning emails to customers when email delivery is available.
6. Save the settings and monitor the next failed-payment recovery before relying on the schedule.

Recovery emails require a configured sending service and a valid customer email. When the UI reports Email delivery is not available yet, the email switch is disabled; automatic payment retries can remain available. A visible setting is not proof that email delivery is available in every environment.

The customer follows the recovery link to update payment information. Expired or canceled recovery sessions cannot be treated as a valid purchase confirmation. Verify provider retries and email delivery before relying on this flow for a live business.

Failed-payment recovery screen in Demo mode · Select to enlarge

Troubleshooting

When contacting support, include the environment, payment provider, affected link's internal name, approximate time, visible error, and whether the problem occurs in demo, preview, or a verified checkout. Share buyer information or payment references only through the appropriate private support channel; never publish API keys, secrets, or full customer URLs.

Account settings and safe operation

Open Settings → Profile to review your account details and PingItNow subscription. Cancellation of your PingItNow subscription is separate from your customers' Stripe or Whop memberships. Account deletion is destructive and affects your payment links, recorded transactions, domains, tracking configuration, and other account data; read the confirmation before proceeding.

Keep production and test environments separate. Use matching payment accounts, webhook endpoints, domains, and tracking-provider settings. Do not copy credentials from an unrelated business simply to make a test connection appear connected.

For a complete release check, verify both the browser return and the payment webhook, then confirm the event in your chosen tracking provider. This closes the loop from checkout to purchase attribution without tying your business to one tracking vendor.