Cause Shield + Raisely
Raisely runs your campaigns and donation pages. Cause Shield wraps them in the operational monitoring most fundraising teams skip — real-time fraud scoring on every donation, uptime checks on the form, AI-written traffic and security reports — all without touching your Raisely setup.
Why pair them
Raisely is great at the campaign layer. Cause Shield watches everything around it. Each Stripe charge is scored for fraud the moment it lands, your Raisely donation page is checked from multiple regions every minute, AI summarises where your donors and traffic actually came from each week, and a monthly external configuration audit catches the TLS, DNS, and security-header issues that pile up between annual reviews. Finance gets the fraud digest, IT gets the uptime alerts, and your fundraising team gets to stay focused on campaigns.
Setup in 10 minutes
Three required steps, one optional. No code review required.
- 01
Sign up + connect Stripe
Create your Cause Shield account and authorise the read-only Stripe connection. Within seconds we’re scoring every charge for fraud — no code changes on Raisely required.
Create your account → - 02
Drop in the tracking snippet
One async script tag. Lights up uptime monitoring, real-visitor analytics, and the goal tracker. Your
tracking_keyis shown on your website’s settings page after sign-up.HTML<script async src="https://causeshield.com/track.js?k=YOUR_KEY"></script>
Paste in your Raisely donation page custom HTML — typically Raisely admin → your campaign → Settings → Custom code → head. Once per campaign is enough; the tracker covers every page on that subdomain.
- 03
Point your Raisely webhook
One URL handles every kind of event Raisely sends — donations, registrations, refunds, disputes. The smart classifier auto-detects what each payload is so you don’t need separate endpoints per event.
URLhttps://causeshield.com/api/wh/YOUR_WEBHOOK_KEY
Add this in your Raisely admin → Settings → Webhooks (or wherever your Raisely workspace exposes outgoing webhook URLs). Subscribe it to all event types — the smart classifier sorts donations, registrations, refunds, and disputes for you.
- 04
Identify donors for Supporter Trails
Optional · PartnerWire one line into your donation form’s success handler and Cause Shield will stitch a donor’s anonymous pageviews to their supporter record. You’ll see the full journey — first landing page, channel, the donation — on every Supporter Trail.
HTML<script> // After your donation form successfully submits: if (typeof window.csTrack?.identify === 'function') { window.csTrack.identify(donorEmail); } </script>The email is sent over HTTPS, hashed server-side with a per-org pepper the moment it arrives, and dropped from memory before any database write. Plaintext donor emails are never persisted on tracking events.
What you’ll see in the dashboard
Three recurring emails. One live dashboard.
Every morning
Daily fraud digest
Plain-English summary of yesterday's flagged donations from your Stripe and webhook stream. Card-testing waves, unusual velocity, suspicious BINs — surfaced before chargebacks arrive.
Every Monday
Weekly traffic report
Where Tuesday's donors actually came from. Channels, devices, goals, and a w/w narrative written by Claude — no tagging plan required.
First of the month
Monthly security report
External configuration audit of your donation domain — TLS, DNS hygiene, security headers, exposed paths. A defensive checkup, not a penetration test.
Running multiple Raisely campaigns or subdomains? Each one becomes its own Cause Shield website, with its own tracking and webhook keys, but the dashboard rolls them up so you see fraud, uptime, and traffic across the whole portfolio in one place.
Raisely FAQ
The questions teams running on Raisely ask first.
Will the tracking script slow my Raisely donation page?+
The script is roughly 3KB gzipped, loaded async with no render-blocking, and beacons events via sendBeacon so it never holds up navigation. Raisely pages already load a fair amount of script; this one is small enough to be lost in the noise. If you measure a regression, tell us — we’re not interested in being the reason your form converts worse.
Does this work with Raisely’s recurring giving?+
Yes. Recurring donations come through Stripe like any other charge, so Cause Shield scores each renewal in real time — including the months when card-testing rings try to hide inside legitimate recurring traffic. When the platform webhook includes a recurring flag we use it to suppress false positives on long-standing supporters.
What if I have multiple Raisely campaigns?+
Every Cause Shield website gets its own tracking_key and webhook_key, so you can scope monitoring per campaign or per subdomain. Growth covers 3 sites and Partner covers unlimited — useful for an org running separate Raisely campaigns for events, peer-to-peer, and direct appeals at the same time.
Do you store donor PII from Raisely webhooks?+
No. The webhook receiver hashes donor email and name with a per-org pepper before anything is persisted, then drops the originals. We keep enough to detect velocity ("same hashed email, three donations in two minutes") without ever knowing the donor’s identity. Raisely itself remains the system of record for donor profiles.
Will Cause Shield interfere with Raisely’s own fraud handling?+
No — Cause Shield is read-only on the payment path. We don’t block, capture, or refund charges; we surface them in your daily fraud digest and (on high/critical risk) email or Slack the on-call person. Decisions to refund or dispute still happen in your Stripe dashboard or Raisely admin.
Start your 14-day trial.
From A$49 a month. No credit card needed for the trial. Cancel any time.