Bring in the Media Content House package
Use plain working language: what will run, what the customer will see and what happened after launch. The Final Product Page HTML is mandatory because this laboratory instruments that exact page; it does not recreate it. Load Don Espadín Example requires no uploads: the complete Media House package, Product Page HTML, SEM setup and campaign-result database are loaded automatically.
What this laboratory can do now
Configure every piece in business terms
This is where the Media Content House Traction Plan becomes executable. For every piece, confirm where it runs, the visual the customer sees, Paid / Owned / Shared / Earned, the exact UTM, investment and KPI target. Product Page pieces are handled as their own group rather than appearing again under Owned.
Build Level 1 first, then configure return-visit nurturing
The loaded Final Product Page HTML is the template. Use the first workspace to place the four buyer-facing Level 1 pieces. Use the second workspace to decide how a returning visitor is nurtured without covering the Product Page title or exposing internal channel names as customer-facing copy.
Configure position, size, message and frequency
Safe placements stay in the lower part of the page so the Product Page headline remains visible.
Decide what happens after each Level 1 click
The first-level banner creates the promise. Here you configure the business action behind it. Product is a contact / advice route; Price changes price or quantity value; Promotion changes the promotional benefit or packaging; Distribution changes delivery or availability. Invalid combinations are blocked.
Operational files for Marketing, SQL, Sales and Payment execution
The three commercial handoffs remain separate: MQL leads go to SQL; direct ecommerce conversion orders go from MQL to Sales / Payment; SQL-won conversion orders go from SQL to Sales / Payment.
Final instrumented HTML
The Media Content House Product Page with Level 1 layout, Level 2 offers, first-party tracking and configured nurturing.
MQL Leads → SQL
Qualified first-party leads with consent, UTM lineage, 4P signal, MQL score and SQL outcome.
Direct conversion orders · MQL → Sales / Payment
Direct ecommerce orders that bypass SQL and move straight to Sales, billing and payment execution.
SQL-won conversion orders · SQL → Sales / Payment
Orders generated after assisted SQL qualification and prepared for Sales / Payment execution.
First-party database · Google Sheets ready
One row per session / cookie with 4P frequency, Buy, More Information, consent, UTM, MQL / SQL status and conversion route.
Campaign KPI Results
Campaign-level impressions, clicks, spend, MQL, SQL, purchases, revenue, CPM, CTR, CPL, CPA and ROAS.
Implementation Pack
ZIP with templates, example data, manual, first-party database, three commercial handoffs, reporting and final HTML.
People who clicked but did not become a lead or order yet
These sessions keep their visitor ID / cookie, original UTM and strongest 4P signal. The table recommends the next value route for nurturing.
| Signal i | Cookie sessions i | Share i | Next-best action i |
|---|
| Campaign / piece i | POSE i | Channel i | Spend i | Impressions i | Clicks i | CTR i | MQL i | SQL i | SQL won i | Direct ecommerce i | Purchases i | Revenue i | ROAS i |
|---|
