Skip to content

SMART COD PRO

What do you need help with?

Choose a topic and go straight to the relevant settings, examples and screenshots.

Installation & connection

Install PRO, connect your subscription and bring over existing settings.

Delivery history & network

Use delivery history from participating stores in the same country alongside your own store’s history. Choose your thresholds and the action at checkout.

Hide Cash on Delivery

Combine checkout conditions to decide when COD is available. Other payment methods remain available.

Conditions reference

Find what each condition checks and how values are matched.

COD fees

Set more than one COD fee and choose exactly when each applies.

Partial COD

Collect a fixed amount or percentage online, then leave the remaining balance payable on delivery.

Email verification

Ask the shopper to confirm their checkout email with a one-time code. No customer account required.

ML risk assessment

Combine delivery history and order context with an available validated model. You set the threshold and the checkout action.

Decision audit

See the matched rule, delivery-history context and protection action together. Investigate a result without guessing.

Troubleshooting

Test your checkout and gather the information needed for support.

Purchases, renewals & refunds

Answers about payment, store limits, renewals and the refund policy.

Premium support, with a proper ticket.

Get help with setup or a checkout issue from your account. Your request and our replies stay together in one ticket, so you can follow the conversation.

Your cookie choice

Essential cookies keep the site working. Google receives limited signals without optional cookies, even if you decline. Analytics enables fuller measurement. Marketing also enables Google Ads and Meta measurement; checkout email hashes are sent only to Google Ads.

Choose what you allow. Optional cookies stay off until you give permission.

Essential

Keep your account, security and checkout working.

Always on

AnalyticsAllow analytics cookies to measure visits, trial starts and confirmed first payments more fully. Limited signals without these cookies are sent even if you decline. MarketingGoogle Ads measures ad conversions using click IDs and a checkout email hash. Meta Pixel and Conversions API measure visits, checkout starts, activated trials and first payments. Optional; no email hashes are sent to Meta.

How measurement works

Google Consent Mode sends limited measurements from site pages without analytics or advertising cookies before you choose or if you decline. These include page and plan events, verified trial starts and first payments, and consent status for aggregate measurement and modeling; they do not provide a complete visitor count. Analytics and marketing cookies remain separate, optional choices. With analytics permission, Google Analytics receives page and plan information, trial starts and confirmed first payments, including a transaction reference, value and tax. With marketing permission, we retain advertising-click identifiers for up to 90 days and link them to trial starts or first payments confirmed by Stripe. For enhanced conversions, we also send Google Ads a normalized SHA-256 hash of the email you provide at checkout. The hash remains personal data and helps Google match conversions to ad interactions. This does not enable personalized advertising. Raw email, name, billing address, card details and password are not sent to Google. Email hashes are not sent to Google Analytics. Password reset, email verification and store connection links are excluded. Google may process data outside the EEA. Your choice, analytics cookies and server measurement records last up to 6 months. Change or withdraw your choice at any time using Cookie settings in the footer. With new marketing consent, Meta Pixel also measures visits to public pages, public subscription plans and checkout starts. It can receive your IP address, browser information, permitted page URL and advertising cookie identifiers (_fbp / _fbc, up to 90 days). Meta may associate these signals with your Meta account and process them outside the EEA. Automatic form-data collection, advanced matching and automatic history tracking are disabled. We do not supply names, emails, billing details, passwords or private account URLs to the Pixel. Private routes and URLs with unrecognized parameters or tokens do not load it. Meta receives no signals from this integration before consent or after refusal. Withdrawal stops the Pixel and removes its first-party cookies. With fresh marketing consent covering Meta Conversions API, our server also reports Stripe-confirmed trial starts and first payments, including a payment after a trial without reopening the browser. We retain the permitted _fbp/_fbc identifiers and checkout browser information for up to 90 days, within the consent period, for this matching. These server events include their actual time, public plan, billing currency and net value and a deduplication reference, with no email, email hash, name, billing details, customer IP or private URL. Earlier Pixel-only permission is not upgraded automatically. Refusal or withdrawal prevents future Meta server delivery and removes the optional server identifiers; already delivered events cannot be recalled through the cookie control.

Google privacy policy · Meta privacy policy