Skip to main content
Connect a MoEngage workspace once and Gradial can work across campaigns, email templates, content blocks, and content-reference offers from a single flow — no context switch into the MoEngage dashboard.

​
What You Can Do

Campaigns

Create campaigns from a prepared payload, search existing campaigns, fetch campaign metadata, change status (launch, pause, stop), and send test campaigns to a list of test addresses.

Email templates

List, fetch, create, and update email templates. Read a template with referenced content blocks resolved into a single merged composition so reviewers see the final output rather than raw placeholders.

Content blocks

List blocks by search text, content type, or status. Fetch, create, and update HTML or text blocks. Name validation is enforced upfront so the API never rejects a create.

Content-reference offers

Build a normalized preview artifact for offers, inbox cards, or campaign shells that reference content managed elsewhere — capturing placement, audience, lifecycle, custom fields, and a template-shaped preview.

​
Prerequisites

  • Admin access to your MoEngage dashboard to generate API tokens
  • Your MoEngage Data Center / API Base URL and Workspace ID from Settings → APIs → API Settings
  • A Gradial organization Administrator role to complete setup

​
How to Connect

1

Get your authentication details from MoEngage

  1. Sign in to your MoEngage dashboard as a workspace admin.
  2. Open Settings → APIs → API Settings and copy your Data Center / API Base URL (e.g., https://api-101.moengage.com). MoEngage assigns this per region — always copy it from the dashboard rather than guessing.
  3. Copy the Workspace ID (also shown as the workspace app_id) from the same page.
  4. Create a dedicated API token for Gradial. MoEngage scopes tokens by API family — generate the one that matches your intended workflows:
Token TypeEnables
CampaignCampaign create/search/meta/status/test and content block authoring
DataRead-only audience and analytics lookups
InformTransactional and inform APIs
PersonalizePersonalization and content-reference APIs
  1. MoEngage returns a workspace and API secret pair. Base64-encode workspace:api-secret — this is the token value you’ll paste into Gradial.
Always create a dedicated MoEngage API token for Gradial rather than reusing a broad shared key. Scope it to the API family you need and add additional tokens later if a workflow requires a different scope. Gradial stores credentials encrypted and never exposes them to the agent.
2

Add the integration in Gradial

  1. In Gradial, go to Settings → Integrations.
  2. Find MoEngage and click + Add.
  3. Fill in the connection details:
FieldValue
Integration NameA display name (e.g., My MoEngage Workspace)
MoEngage API Base URLYour data-center origin (e.g., https://api-101.moengage.com)
Workspace IDThe workspace app_id
API Token Typecampaign, data, inform, or personalize
API TokenYour Base64-encoded workspace:api-secret token, with the Basic prefix
  1. Click Save. Gradial validates the workspace, base URL, and credential scope during setup.
3

Assign to an Environment

  1. Go to Settings → Environments and select the Gradial Environment where MoEngage should be available.
  2. Add the MoEngage integration to that Environment.
  3. Repeat for any additional Environments.

​
How It Fits Into Broader Workflows

Use caseHow to use it
End-to-end email authoringAuthor email templates and content blocks from the same Gradial thread that produced the brief, copy, or designs
Campaign executionPrepare a payload, run a test send, change status, and verify with a follow-up search — all from chat
Content-reference offersStage inbox messages, in-app cards, or offers whose creative lives in a DAM or CMS — the offer artifact captures placement, audience, and lifecycle before any MoEngage write happens
Cross-integration campaignsCombine MoEngage with Bynder for approved creative, AEM or Drupal for landing pages, and Gradial’s asset search to assemble a campaign end-to-end in one workflow
Example workflow:
  1. Start with a campaign brief — for example, “send a welcome email to new sign-ups.”
  2. List existing content blocks to find reusable hero copy or footers; create or update blocks as needed.
  3. Draft the email template with resolved HTML and any content block references, then read it back to confirm the merged composition.
  4. Build a content-reference offer artifact capturing audience, placement, and lifecycle so reviewers can preview the card before any send.
  5. Send a test campaign to the QA distribution list and iterate until the rendered output is right.
  6. Create the live campaign and change status to launch it once approvers sign off.
  7. Re-run campaign search to confirm the campaign is active and surface the artifact in the thread for stakeholders.

​
Support

Contact your Gradial onboarding lead or email [email protected] for help with setup.