What do you like best about Insider One?
Conceptual flexibility when implementations align: When CSS selectors are consistent, the platform can support inline campaigns across multiple domains—as was demonstrated to us—suggesting solid potential for multi-site personalization once foundations are correct.
Panel logic makes sense in principle: The idea of using panels to group domains with shared templates/div structures is logical for scaling in-line campaigns and system rules—if the upfront scoping is done well.
Recent engagement from a technical lead: In the past week, we’ve seen a more structured recap of open items (panels/domains, dynamic URLs, Tealium data layer approach, user attributes schema) and a willingness to investigate workarounds (e.g., conditional logic for partner_id, alternative approaches to placements).
User data model work is underway: Finalizing a user attributes schema should help unlock testing and expand use cases once the core integration issues are resolved. Review collected by and hosted on G2.com.
What do you dislike about Insider One?
Onboarding delays and missed commitments:
We submitted the initial integration on January 31 with a stated 2–4 week timeline for System Rules.
Months later, it was still pending.
Last-minute cancellations impacting our team:
Onboarding and training sessions have been repeatedly pushed at the last minute, making it extremely difficult to reassemble the right cross-functional group on short notice. These disruptions have materially hindered progress and contributed to our missed early-April migration target from our other Personalization tool.
Lack of clarity on core implementation topics:
No one at Insider was able to give us a definitive plan for how to use panels for domain groupings given our hybrid site structures, nor a clear approach for embedding a single inline banner in multiple areas at the same time across same or similar sites.
Design Studio limitations and productivity friction:
The inability to create custom HTML/CSS/JS templates from scratch, the absence of an “undo” capability, and uncertainty around dynamic URLs have slowed design and iteration. This creates rework and makes it harder for an experienced team to move quickly.
Technical implementation gaps and rework loops:
We’ve encountered script issues during our first campaign usage and are still waiting on conditional logic updates (e.g., based on partner_id) and multi-domain support that doesn’t require a unique campaign/URL per domain.
We’ve also had to revisit prior discussions due to limited awareness of platform capabilities, which is both inefficient and frustrating.
Data layer and events uncertainty:
Native Tealium data layer support is not on the roadmap, and while a custom solution was being explored, this should have been a known issue and clearly communicated constraint at the outset.
Communication, task ownership, and accountability: We’ve felt heavily neglected in onboarding and support.
Too often, our account team has functioned as non-technical intermediaries rather than problem-solvers, leading to bottlenecks, unclear ownership, and slow handoffs.
Platform fit concerns for our scale/complexity:
Based on our deep-dive, we now know the platform cannot meet our requirements without substantial iteration and updates.
Instead of upgrading our current capabilities with Insider, we’d be regressing.
In conclusion, our current website personalization tool dances circles around Insider and costs 85% less. Review collected by and hosted on G2.com.
