What We Do

Custom Data Enrichment at a Glance

The Custom Data Enrichment team provides tailored data qualification and tagging services on top of the standard LaunchMetrics platform offering. When a client's measurement needs go beyond what the platform delivers out of the box, this team steps in to ensure every relevant media clip is accurately categorized, labelled, and delivered to specification.

The team currently manages a range of active projects across different industries and channels — including print, online, and social media — each with its own tagging logic, delivery cadence, and quality standards.

Examples of Customizations Across Active Projects

Category Tagging

Classifying media clips by product category, product line, or business division based on article content and brand-specific rules.

Campaign & Collection Tagging

Matching coverage to specific campaigns, collections, or activations — including custom date windows and keyword logic.

Tonality & Coverage Type

Qualifying clips by editorial tone (positive, neutral, negative) and coverage format (editorial, PR, corporate, event, etc.).

Spokesperson & Event Tagging

Identifying and attributing coverage to named individuals, ambassadors, or brand-owned events.

Manual Data Integration

Uploading and enriching client-supplied content (e.g. Instagram stories, PPT assets) that sits outside standard platform ingestion flows.

📌 Note: Until now, all customizations have been handled fully manually. Going forward, certain workflows may be supported by AI-assisted automation, enabling faster turnarounds and higher volumes where applicable. At the same time, the progressive rollout of advanced enrichment capabilities on Discover is expected to gradually reduce the need for custom solutions over time.

How to Request a Customization

The Request & Feasibility Process

Any new customization — whether for an existing client or a prospective one — must go through a structured request process. This ensures the team can assess feasibility, align on scope, and plan capacity before any work begins.

Step 1 — Submit a Ticket

All requests are initiated via a ticket. The ticket should describe the client's need in plain terms — there is no requirement to define how the customization should be implemented technically. The team will evaluate the request and propose the appropriate approach.

Step 2 — Feasibility Check

Once the ticket is received, the Custom Data Enrichment team will conduct a feasibility assessment. This covers two dimensions: whether the customization is technically achievable within the platform, and whether the team has sufficient capacity to take it on given current commitments.

Step 3 — Scope Definition

If feasible, the team will define what the work involves operationally — tagging logic, channel scope, frequency, quality checks, and any platform-specific constraints.

Step 4 — Pricing

Customizations are a paid service. Standard pricing is available on Salesforce. For custom scopes the Custom Data Enrichment manager can support the business team in defining an appropriate pricing reference based on the confirmed scope and estimated volume. The final price to be proposed to the client remains the responsibility of the business team, taking into account the client relationship and any ongoing commercial context.

What to Include in the Ticket

To enable a thorough feasibility assessment, every ticket must clearly specify the following:

• Client need — what the client wants to measure or track, in their own terms
• Delivery deadline — when enriched data must be available to the client
• Estimated volume — number of clips or records expected (estimates are acceptable)
• Channel & market scope — which media channels and geographies are in scope
• Frequency — one-off delivery, monthly, ongoing, or campaign-based
• Any existing reference — if similar work has been done before for this client, reference it
  
   

📋 Submit a request here: [Discover Project] Qualification Project Activation

Active Projects

How Active Projects Are Managed

Every active customization project is assigned a dedicated project owner and a backup within the Custom Data Enrichment team. Their role is to ensure the project remains accurate, up to date, and delivered on time — and to serve as the primary point of contact for the relevant Customer Success Manager.

When a question or ambiguity arises during tagging, the project owner will reach out directly to the CS Manager or, where agreed, to the client — to resolve it and maintain data quality. This escalation happens proactively and does not require separate coordination from the business team.

Tickets Required — Active Project Communications

Any update, change, or decision affecting an active project must be communicated through a ticket. This ensures the team has a clear record and can plan accordingly. Specifically:

• Changes to tagging logic, scope, or delivery requirements for an ongoing project
• Issues or anomalies identified during regular project maintenance
• Temporary suspension or pause of a project
• Project closure — whether due to contract end, client churn, or a deliberate decision to discontinue the customization

Informing the team via informal channels (Slack messages, email threads) is not sufficient on its own. A ticket ensures traceability and proper handover if needed.

 

📋 Submit a project update or closure: [Discover Project] Ongoing Qualification Project Update