How it works: three surfaces, one platform
UserEvidence Advocacy supports three modes for how advocates interact with your program. You don’t have to pick just one, and understanding the difference helps you design a program that actually gets adopted.
Option 1: Hub (Destination Advocacy)
The Hub is the full standalone experience. Advocates navigate to a dedicated URL (like community.yourbrand.com) and get the complete portal: missions (activities they can complete), rewards, leaderboard, levels, community forum, and more.
This is the default setup and works well for programs where you want to build a dedicated community around your brand.
Option 2: Embed (Embedded Advocacy)
With the Embed mode, the Advocacy portal loads inside an iframe on another site, like a customer community built on Higher Logic Vanilla or Gainsight, or any external web app you already own.
Missions, rewards, levels, and the leaderboard surface as carousels and cards that live within the host page. Advocates never have to leave the tool they’re already in. This is especially powerful when your advocates are already active in an existing community or portal and eliminates the friction of learning a new tool.
Option 3: Standalone (Single-mission links)
Standalone mode is a direct link to a single mission. Think of it as a shareable URL you send via email or Slack: yourbrand.com/mission/123.
The advocate lands directly on the mission, completes it, and there’s no hub to log into.
It’s the fastest way to activate advocates for a one-off ask, a timely product launch, or a G2 review push, without any portal setup required.
How to set it up
- Hub (Destination) — No setup needed. Every brand gets a dedicated portal URL out of the box — just share it with your advocates and they’ll get the full experience.
- Embed — Go to Tools → Integrations, find your community platform (Gainsight, Higher Logic Vanilla, or oEmbed), click “Learn More” or “Copy Link” and follow the step-by-step guides to add the embed to your community.
- Standalone — No setup needed. Copy the URL of any individual mission and share it directly (via email, Slack, etc.) – advocates land right on that mission.
Many teams start with Standalone missions to test engagement, layer in Embed if they have an existing community to wire into, and build toward a full Hub as their program matures and the case for a dedicated destination becomes clear.
What becomes possible
The biggest unlock here is that you don’t have to choose between running a serious advocacy program and having the bandwidth to pull it off.
Embedded missions inside your existing community mean advocates don’t have to learn a new destination. Standalone mission links mean you can run a targeted G2 review push or a beta feedback campaign in a single afternoon, no hub required.
Teams that start with these lighter-weight surfaces typically see faster initial activation and less friction getting their first advocates to engage, which makes building the case for a full program much easier over time.
