Wrike Media Connect is a zero-dependency embeddable widget that surfaces live campaign data from Wrike directly inside your media planning, reporting, and workflow tools — in a single script tag.
Choose the integration mode that fits your workflow. Each mode is self-contained and independently configurable through standard HTML attributes.
Fetch and render live Wrike campaign data in your application. Choose exactly which fields to display — campaign name, dates, budget, client, status, and more. Includes a manual refresh button and an in-page Wrike modal.
Show current campaign data and let authorised users push changes back to Wrike with a single click. Supports both static payload configuration and dynamic payloads set at runtime by the host application.
Submit a fully pre-configured campaign creation payload to Wrike without leaving your application. The widget automatically appends the current date and time to the campaign name at the moment of submission, ensuring every created campaign has a unique name. Returns the new campaign ID and a direct Wrike link on success.
Every design decision was made to minimise integration friction and maximise reliability in production host applications.
The widget renders inside a Shadow DOM. Your host application's CSS cannot bleed in and the widget's styles cannot bleed out — zero risk of style conflicts regardless of how complex your host page is.
Campaign data is surfaced through the browser's standard Custom Events API on the target element. No proprietary SDK or callback convention to learn — just addEventListener.
Authenticate once, unlock everything. A single Wrike login token is shared across all widget instances on the page and across browser tabs via BroadcastChannel — users never see multiple login prompts.
Place any number of independently configured widgets on the same page. Each runs in its own IIFE closure with its own Shadow DOM, event scope, and data fetch cycle.
Four color attributes (primary, background, text, accent) let each widget match the host application's brand identity — without touching a stylesheet.
Rename any Wrike field label globally via a single localStorage key. Set once by a Tech Admin; applied to every widget instance across the entire application automatically.
No npm. No bundler. No framework requirement. The entire integration is a
<div> and a <script> tag.
data-* attributesaddEventListener<!-- 1. Place a container --> <div id="campaign-widget"></div> <!-- 2. Include the widget script --> <script src="./wrike-media-connect.js" data-target="campaign-widget" data-campaign-id="IEAC7PRTI5SVIV6V" data-display-attr='["campaignname", "campaignstartdate","client"]' data-color-primary="#1E40AF" ></script> <!-- 3. Listen for campaign data --> <script> document.getElementById('campaign-widget') .addEventListener('wrike-media-connect:data', (e) => { console.log(e.detail); }); </script>
Whether you're evaluating the business value or planning a technical integration, the pilot program has a place for you.
Evaluate the widget's ability to surface Wrike campaign data inside the tools your teams already use daily — without requiring a full Wrike login for every user.
Evaluate integration effort, review the technical architecture, and build a proof-of-concept integration against real Wrike staging data during the alpha period.
<script> tagA typical pilot engagement runs 2 to 4 weeks across four structured phases. We begin with discovery to confirm fit and scope before any integration work is undertaken — ensuring both sides commit only when there is a clear and viable case to proceed.
To ensure the engagement is productive for both sides, pilot partners are expected to come prepared with dedicated technical resource, a clear understanding of their own product and data requirements, and a confirmed use case before the Discovery phase begins. The more domain knowledge and context your team brings to each phase, the faster and more effective the engagement will be.
The alpha program is a structured, time-boxed engagement. Pilot partners receive dedicated support and have direct influence over what ships in the GA release.
The pilot is a structured, four-phase engagement — not open-ended access. Each partner works through a defined process with clear gates and outcomes, supported by the MediaConnect team at every step.
Register your interest and our team will reach out within 5 business days to discuss your integration use case and confirm your pilot access. Spots are limited to ensure each partner receives dedicated support.
✦ Open the Registration Form →By registering you agree to provide integration feedback during the alpha period. Your data is handled in accordance with WPP's internal data policies.
.js file
included via a standard <script> tag. It works in React, Vue, Angular,
or plain HTML pages.
localStorage and shared across all widget instances — subsequent visits are
seamless. Users do require Wrike credentials during the alpha period.
<script> tag creates a fully independent widget instance in
its own Shadow DOM. You can have any number on a single page, each pointing to a different
campaign ID and using a different visual configuration. They all share the same authentication token,
so users only log in once.
data-update-payload attribute —
only those fields are written back; all other campaign fields are untouched.
data-color-* attributes control the header, background, text, and
accent colors. Field labels can be remapped globally by a Tech Admin via a single
localStorage key. Because the widget uses Shadow DOM, you do not need to
worry about CSS conflicts with your host application's stylesheet.
Have a specific use case in mind or technical questions before registering? Reach out directly to the people building and supporting the program.