WMC End to End Limitations
Table of contents
About End to End Limitations
WMC was designed to offer a single application for all campaign management and e-commerce capabilities. It can be used to create order pages, creatives, journeys, efforts - all in one place.
While WMC can be used end to end today, the development focus has been primarily on the e-commerce aspects as we move to transition from Funnelcake and Opium. Therefore, some of the reporting and features users are used to when using IRIS will not be available when using WMC.
Below is a list of heavily used features, fields and statistics that will not be available when using WMC end to end but WILL be available when using the WMC to IRIS connection.
This list is focused on eCommerce/paid. Additional gaps may exist for lead gen.
Please note that while many of these items will be available when using WMC in the future, it’s unlikely that there will be exact parity between IRIS fields/functionality and WMC, even when it is fully developed.
WMC Limitations
IRIS effort statistics will not be available in WMC (or in BI reporting – which has always been the case), including but not limited to:
Clicks to order form | Total abandons | Conversion rate |
Revenue per click to order form | CTR Order Form | Abandon Rate |
Revenue Per Name |
|
|
Promo abandon emails from Blueshift will not be able to be triggered from WMC
Cart abandon emails from Blueshift will not be able to be triggered from WMC
External Partners cannot store partner URLs or have a “Partner view” in WMC
Recurring efforts are not available in WMC
You will not be able to compare the performance of testing groups in WMC on the efforts listing or details pages
Visual editor IS available in WMC, but we don’t recommend using it until we are able to define and implement needed improvements
Vanity URLs are not available in WMC
Agora swaps are not available in WMC
Pop-ups are not enabled in WMC
You cannot combine lead gen and ecomm in the same journey
BI Reporting
No IRIS fields will be populated for WMC promo codes – including but not limited to:
IRIS Multivariate ID | IRIS Destination | IRIS Page 1 |
IRIS Advertisement | IRIS Effort Tag | IRIS Placement Name |
IRIS Campaign | IRIS Effort Type | IRIS Segment Name |
IRIS Testing Group | IRIS Testing Sub Group | IRIS Tree Name |
We are currently unable to differentiate between primary and upsell orders for WMC promo codes
We can differentiate between primary and cross-sell orders using back up logic (i.e. any item that is not the assumed primary item (using back up logic) is labeled a cross-sell)
We are currently unable to link together journey testing groups in reporting (WMC’s version of multivariate groups), so users will have to look up and compare the individual promo codes
We are currently unable to include WMC promo codes with no orders in mailing data
Selections made in the Spend and Revenue Allocation section of WMC will not be reflected in reporting. We recommend NOT entering ad spends in WMC for the time being.
WMC custom fields are not currently reflected in reporting
Still need help?
We know this can be frustrating. To get further help please open a Support ticket.