Data sources studio

With Data sources studio, you don’t start from a blank model. When your organization is created, Piano Analytics preloads a behavioral source tailored to your industry (Publishing, Retail, Banking, Travel) or, if none applies, Core Analytics. Your tracking plan is ready: you fine‑tune it, hand a developer‑ready guide, and verify data collection. From “nothing in prod” to “board ready” in a few clicks.

This first release brings three interfaces working together:

• Tailor: adapt the proposed tracking plan.

• Implement: generate a shareable implementation guide for developers.

• Monitor: check that events and properties are collected as expected.

Coming next:

• Discover: data sources catalog.

• Data sources studio (installed sources list) within Data Management (by year‑end).

• Activate: one‑click activation for contextual sources.

Data sources studio is currently available only for new Piano Analytics clients. The interface will be opened for existing clients in the coming months.

Access and navigation

• Open Piano Analytics.

• From the tool switcher, go to Data Management.

• In the left menu, open Data sources studio: you land directly in Tailor.

Access rules:

• Tailor and Monitor: require Data Management permissions.

• Implement: reachable via a public link (GUID) you can share with developers; validity 6 months, not revocable.

The 3‑step journey

1. Tailor: select, detail, and prioritize what should be collected.

2. Deploy to Implement: generate or update the developer guide (same link is updated).

3. Monitor: verify collection over the last 30 days, focusing on “Board Required”.

Pro tip:

• Start with “Board Required” items (lock icon). They’re enough to automatically deploy an out‑of‑the‑box (OOTB) board for your vertical.

Tailor: design your tracking plan

Tailor creates a clear, actionable implementation plan, based on your industry.

What you see:

• Two complementary views on top:

  • Events View: left column lists events; right panel shows their linked properties.

  • Properties View: left column lists properties; right panel shows their linked events.

• Collapsible categories for easier reading.

• A lock icon for “Board Required” items (tooltip “Board Required”).

• A “Values” column to document default values to pass.

• An “i” button at the end of property rows: key, type, description, scope, category.

• Header actions: Monitor, Deploy to Implement (or Get Implement Link).

What you can do:

• Add or remove events from your plan.

• Link/unlink properties to events (or vice‑versa in Properties View).

• Define a trigger at event level (when to send it).

• Set a default value at property level (e.g., Page = “Home Page”) to guide developers.

• Jump between views using the small hover arrow (cross‑navigation).

Good to know:

• Tailor lists only “processed” properties (the ones your developers must send). Properties handled automatically by the SDK/processing are hidden.

• “Board Required” items cannot be removed.

• Supported property types: string, integer, date, array string, bool (and, in some cases, decimal).

• Tailor changes are live. To expose them in the developer guide, click “Deploy to Implement”.

Implement: hand a turnkey guide to developers

Why a dedicated step?

• To deliver a self‑customized guide that reflects your Tailor selection, values, and “Board Required” priorities. Get data by copy pasting from implement.

Link rules:

• Public link (GUID), valid 6 months, not revocable.

• After every Tailor change, click “Deploy to Implement” to update the same GUID.

Three screens:

1. Implementation Context

   • Technology: JavaScript (Web) for now (Android, IOS and GTM soon).

   • Target Site (Site ID): pick your site; the ID flows into snippets.

   • Piano Analytics Collection Domain: choose the collection domain (including CDDC setups).

2. SDK Setup & Privacy

   • Include and configure the Piano Analytics SDK with a ready‑to‑copy snippet.

   • Set consent (Opt‑In, Essential, Opt‑Out) and User ID.

3. Sending Events

   • Left column: all events, locks on “Board Required”.

   • Right panel: pa.sendEvent() snippet for the selected event.

   • Each property is commented (type + “board required” when applicable).

   • Actions: copy code; Hide Comments to hide inline comments.

Code snippets (JS excerpts — exact script URL is provided in Implement):

// 1) Load SDK with your context
(function (_config) {
    var script = document.createElement("script");
    script.src = "https://tag.aticdn.net/piano-analytics.js"; // Indicative; use the URL shown in Implement
    script.async = true;
    script.crossorigin = "anonymous";
    script.dataset.config = JSON.stringify(_config);
    document.head.appendChild(script);
})({
    site: 547656,
    collectDomain: "bpwphks.pa-cd.com",
    consentDefaultMode: "opt-in"
});
// 2) Consent
pa.consent.setByPurpose("AM", "opt-in");   // or "essential" | "opt-out"

// 3) Send an event
pa.sendEvent("internal_search_result.click", {
    ise_keyword: "",      // string
    ise_page: 0,          // integer
    ise_click_rank: 0     // integer, board required
});

Sharing tip:

• Share the Implement link through a secure internal channel (the link is public).

• After any Tailor change, “Deploy to Implement” before sharing again.

Monitor: verify collection and prioritize

Monitor provides a matrix that shows, for each event × property, whether you collect what you planned.

What you see:

• Y‑axis: events (collapsible categories).

• X‑axis: properties (collapsible categories).

• A two‑arrows button to flip axes.

• Locks on “Board Required” items.

Cell statuses:

Good to know:

• Time window: last 30 days.

• All “Board Required” turning green triggers automatic deployment of your vertical’s OOTB board.

Reading tip:

• Start by scanning locks and hunt for grey dots first: these are your top actions.

• Orange dots (not expected) highlight implementation drifts: a property may be sent under the wrong event.

OOTB board: when is it deployed?

• Automatically once every “Board Required” is green in Monitor.

• If one later turns grey, the board remains deployed but may become partially inaccurate.

Pro tip:

• After each production release, check Monitor: when all locks are green, your OOTB board is ready.

First‑deployment checklist (30–60 minutes)

• In Tailor:

  • Add/remove events to match your scope.

  • For each key event, define a clear trigger.

  • For sensitive properties, set default values when helpful.

  • Prioritize “Board Required”.

• Publish to Implement:

  • Click “Deploy to Implement”, then share the link.

  • In Implement, pick Technology = JavaScript, your Site and collection domain.

  • Copy SDK initialization and the consent policy (Opt‑In/Essential/Opt‑Out).

  • Copy snippets for priority events.

• Control in Monitor:

  • Check the last 30 days.

  • Tackle grey dots on “Board Required” first.

  • Fix not‑expected sends (orange dots).

Current release limitations

• Single preloaded source per organization (soon deploy as many sources as you like).

• Supported SDK: JavaScript only (iOS, Android, Google Tag Manager coming soon).

• Monitor: no “Board Required” filter, no drill‑down; fixed 30‑day window.