Support
How to get help, file a useful bug report, and report a security issue responsibly.
Before you reach out
A few quick checks resolve most questions faster than email:
1 · Check the FAQ
Most common questions — analytics, permissions, redirect handling, the Deal Feed, missing tags — are answered in the FAQ.
2 · Skim the user guide
For the specific feature you're using (Convert, Telegram/webhook broadcast, Deal Feed, Mobile Preview, Redirect Tracer, reminders, tools) — see the User guide.
3 · Confirm your version
Dashboard → More → About should report version 1.0.12. If not, update first — the issue may already be fixed.
4 · Confirm your browser
Requires Chrome 116 or newer (Manifest V3). Older builds are unsupported and several features will not load.
How to get help
[email protected] — primary channel for questions, bugs, and feature requests.
Website
deals.group — product information and links.
About
deals.group/about — about the publisher.
For general questions, email is fine. For bugs, please follow the checklist below. When you write in, mention the extension by name (DealsGroup Affiliate Engine) and include your version number, since support covers multiple releases.
How to file a good bug report
The more of the following you can provide, the faster we can help. Email it to [email protected].
Extension version — from Dashboard → More → About (currently 1.0.12).
Chrome version — from chrome://version — and your operating system.
Exact steps to reproduce — what you clicked, in order, from a known state.
What you expected versus what actually happened.
The input link and the output link, if it's about conversion (redact your tag if you prefer).
Which feature was active and any error shown in the UI, copied exactly.
Optional: the service-worker console log. Enable verbose logging with chrome.storage.local["dg.debug"] = true, reproduce, then copy the output from chrome://extensions → Details → Inspect views: service worker.
Security disclosure
If you believe you have found a security vulnerability, please report it privately by email — do not post details publicly.
What to include
A clear description and potential impact.
Steps to reproduce or a minimal proof-of-concept.
Extension version (1.0.12), Chrome version, and OS.
Any relevant non-sensitive logs or screenshots.
What NOT to send
Real bot tokens, API keys, webhook secrets, or custom headers.
Real credentials of any kind, or other people's personal data.
A demo requiring us to log into a live third-party account with your real secrets — describe the mechanism instead.
Subject: SECURITY: DealsGroup Affiliate Engine. Please give us a reasonable opportunity to investigate and ship a fix before any public disclosure. See Security for the design background.
Response expectations
DealsGroup Affiliate Engine is maintained by a small team, so support is best-effort with no guaranteed response time. We aim to acknowledge email within a few business days. Security reports are prioritized. Including the details above (version, Chrome version, exact steps, console output, sanitized export) significantly speeds up a resolution. Clear, reproducible reports are handled first.
Common quick fixes
Missing tag / wrong link — verify the store's tag and network. The extension refuses to tag suspicious IDN-homograph (xn--) hosts.
Reminder didn't fire — confirm OS notifications are allowed. Missed reminders fire on startup within a 24h grace window.
Import rejected — likely unknown keys, wrong shapes, or a URL failing the SSRF check. Imports roll back on failure.
Deal Feed won't show messages — it's opt-in and receive-only; click Connect. Live-only; auto-disconnects after 5 min.
Analytics — on by default; turn it off any time in Settings → Behavior.
Add DealsGroup Affiliate Engine to Chrome
Free on the Chrome Web Store — works on Chrome, Edge, Brave, Vivaldi and Arc.