Support
We're here to help store owners and shoppers.
Email support@webnotics.solutions with your store's address and what you were doing. We reply within 1 business day.
New to CartPass? Start with the documentation.
What to include
- Your store's address (the published site URL).
- What you did, what you expected and what happened instead, with any message you saw word for word.
- The time it happened and the email address involved, if it concerns a shopper or a sent email.
- For email problems, the message's row in Emails → Transactional → Email history. For webhooks, the delivery in Developer → Webhooks → Logs.
- Never send passwords, API keys, webhook secrets or client secrets. If one may have leaked, reset it in the dashboard first.
Guides
- Install and uninstall: Install, Disconnect or uninstall
- For shoppers: Sign in, Address book, Order tracking
- Access and sign-in settings: Roles, Authentication, Permissions, Team
- Email: Emails
- For developers: Developer, API keys, Webhooks, Playground
Getting started
- Install CartPass in Webflow and choose your store.
- Publish your site in Webflow. "Sign in", "Create account" and "My account" appear in your navigation.
- Open the dashboard any time from Webflow: Apps → CartPass → Open App.
Common questions
The Sign in button doesn't show on my store.
Publish your site after installing. If you use a custom domain, check it's listed in Settings → Storefront → Allowed domains.
A shopper can't see their orders.
Orders appear after the shopper confirms their email, and only for orders placed with that same email.
Can I add customers myself?
Yes. In the dashboard open Customers → Add customer. They get an email to set their password.
How do I show content only to some customers?
Create a role (for example "Wholesale") under Roles, assign it to customers, and add data-af-role="wholesale" to any element in Webflow.
Where are card details stored?
Not with us. Payments are handled by Webflow's checkout and payment provider. We only see the card brand and last 4 digits.
How do I remove CartPass?
In the dashboard open Stores → Disconnect, publish your site, then uninstall CartPass in Webflow. Full steps, and what to do if you uninstalled first, are in the documentation. See Data deletion for what happens to your data.
Troubleshooting
Google, Facebook, GitHub or LinkedIn sign-in says the redirect URL doesn't match.
Add the exact callback address CartPass shows under Authentication → Sign-in methods to your app at the provider. It looks like https://cartpass.app/oauth/google/callback, with the provider's name in place of google. It must match character for character, including https and no trailing slash. Then check the client ID and secret you saved in CartPass are the ones from that same provider app. See Authentication.
Social sign-in says the email isn't confirmed.
CartPass only signs a shopper in with an email the provider says is verified. For GitHub, the primary email on the account must be verified. A shopper without one can use another sign-in method.
My sender address won't verify.
Add every DNS record shown for the sender at your domain's DNS host, exactly as given, then press Verify. Changes can take from a few minutes to a day to appear. Make sure you own the domain, that you haven't typed it twice in the host name (some DNS hosts add the domain automatically), and that you have only one SPF record for the domain: merge our include into the existing one instead of adding a second. See Emails.
My campaign is blocked and I can't send it.
Campaigns need a verified campaign sender and a business address (Settings → Legal & business), because both go in the footer of every message. New accounts can send 24 hours after sign-up, and up to 3 campaigns can be started in any 24 hours. The campaign page lists what is missing.
A shopper didn't get a campaign.
Campaigns go only to shoppers with a confirmed email who turned on News and offers, and never to addresses that unsubscribed, bounced or complained. The reach count in the campaign wizard shows how many are excluded.
My webhook signature doesn't match.
Compute the signature over the raw request body, exactly as received, before any JSON parsing, using the timestamp and the endpoint's signing secret as shown in Webhooks. Check you are using the secret of that endpoint, not an API key, and that your server's clock is correct. After you rotate a secret, the old one keeps signing for a short time, so accept either until it expires.
My API call returns 401, 403 or 429.
401 means the key is missing, wrong or revoked. 403 means a read-only key tried to change something; use a key with full access. 429 means more than 600 requests per minute on one key; slow down and retry. See API keys.