Best Practices for Omnichannel Experiences

sometimes you may need to deviate from these guidelines for omnichannel experiences, but you should aim to follow them whenever possible to keep your engine api implementation as effective and as efficient as possible make as few calls as possible to the engine api to minimize round trips and maximize load time for your application use the top level "channel" parameter to identify your account instead of the separate "account" , "domain" , or "instance" parameter inside the docid\ dspilr3g1cifaeeylsqsb event doing so allows you to report events without requesting a decision docid\ mchjagbkmagu2x17bretp as early as possible for initial decisioning, provided that the context needed for the decision is available persist monetateid / deviceid , preferably monetateid for docid\ zfxs45ymf6aicwwkkgxcc , such as server side integrations or mobile apps, there is no way for monetate to set the mt v cookie your application code must keep track of the monetate id build your application around the docid\ lqst4abe9zqx k3ta8nnh for flexibility you don't want to have to redeploy every time you do something new maintain a fallback in case no experiences are running or you experience issues connecting to engine api (such as "driving through a tunnel") send all applicable events, especially for pure engine api implementations