Prerequisites for Mapp Fashion Onboarding

Prev Next

Introduction

This document outlines all the prerequisites required to complete the onboarding process for Mapp Fashion successfully.

Please review and provide the requested information before implementation begins.


1 Use Cases

1.1 All Use Cases (including Enriched Product Attributes)

1.1.1 Technical Contact Information

Provide details of a technical contact person to ensure we can reach out regarding:

  • Website or domain issues

  • Third-party access

Send this information to your Account Manager.

1.1.2 Sample Product List

Provide a CSV file containing a sample of your products.

The file must include the required columns listed in the Attributes Reference.

Example file:

sample_product_feed
3.73 KB

1.1.3 Product Feed Transfer Setup

A complete product file with all required attributes must:

  • Be available via SFTP

  • Refresh at least once per day to ensure accuracy

Provide Mapp with your SFTP credentials and configuration details. If IP allowlisting is in place, make sure Mapp IP addresses are allowed.


1.2 Recommendations

Applies to:

  • Personalized Outfits

  • Similar Items

  • Themed Emails

  • BAU Emails

  • Outfit Emails

1.2.1 Domain Delegation

Delegate and confirm your chosen subdomain for tracking user behaviour and activity on your website.

Mapp only uses the delegated subdomain; your primary domain remains unaffected. Follow instructions here: Delegate a Domain.

Once delegated, provide your subdomain address to your Account Manager so we can create the DNS records and finalize setup.

1.2.2 Google Tag Manager (GTM) Access

We require edit access to your GTM account to configure data collection.
We will:

  • Send you a list of email addresses that need edit rights

  • Carry out all changes in a dedicated workspace

You remain responsible for reviewing, testing, and publishing once setup is complete.

1.2.3 Sample Data (Orders / Returns)

Provide two CSV files: one for Orders and one for Returns.

Each file must:

  • Include a header row and one row per purchased item

  • Use a unique, incrementing EntryId for each record

  • Maintain consistent product and customer identifiers (matching Product Feed and Event Tracking)

See Attributes Reference for required columns.

1.2.4 Live Data Feed (Orders / Returns)

Complement sample feeds with daily refreshed CSVs available via SFTP.

Share SFTP credentials and add Mapp IPs to the allowlist if applicable.

1.2.5 Historical Orders / Returns Data

Provide a historical dataset covering at least 12 months (preferably 24).
Include:

  • Header row

  • One row per item purchased (multiple quantities of the same item must appear as separate rows)

  • Unique incrementing EntryId starting from 1

This data supports model training and analysis.

Note:

The Product and Customer identifiers must match the Product Feed and Event Tracking.


1.3 On-Site Recommendations (Hosted Widgets)

Note:

Product and customer identifiers must match the Product Feed and Event Tracking.

1.3.1 Widget Design Assets

To customize widgets, provide:

  • Font color (HEX code)

  • Font family (include .ttf or .woff2 if custom; also include a web-safe fallback such as Arial or Helvetica)

  • Font size and line height (in pixels for headers, subtitles, and body text)

Only one round of design changes is possible after implementation, so ensure details are final.

1.3.2 Widget Placement

Prepare empty DIVs with static HTML IDs on your Product Detail Pages for widget injection (e.g., Personalized Outfits, Similar Items).

Share these DIV IDs with Mapp to ensure correct integration.


1.4 Themed, BAU, and Outfit Emails

1.4.1 Email Block Design

Provide design specifications for:

  • Font color (HEX code)

  • Font size and line height for headers, subtitles, and body text

Custom fonts are not permitted.
Only one round of design changes will be possible after implementation, so finalize design details in advance.

1.4.2 Theme Brief

(Applies to Themed Emails only)
Provide a theme brief including:

  • Planned send date (or first send date for recurring campaigns)

  • Theme description

  • Product inclusion criteria

  • Preview/mockup of recommendation slots in the email

This allows the Stylists team to align themes with your marketing strategy.


2 Prerequisites Matrix

Prerequisite

Enriched Attribute Export

Personalized Outfits

Similar Items

On-Site Recommendations (Hosted Widgets)

Themed Emails

BAU Emails

Outfit Emails

1.1.1 Technical Contact Information

1.1.2 Sample Product List

1.1.3 Product Feed Transfer Setup

1.2.1 Domain Delegation

1.2.2 GTM Workspace Access

1.2.3 Sample Data (Orders / Returns)

1.2.4 Live Data Feed (Orders / Returns)

1.2.5 Historical Orders / Returns Data

1.3.1 Widget Design Assets

1.3.2 Widget Placement

1.4.1 Email Block Design

1.4.2 Theme Brief