Getting "Not plugged in" in one place and "Conflicting app ID" in another
Hey, I am the intern who got handed the A/B testing project this sprint so bear with me. The site already had a Croct script tag install in the base layout from before my time, and I added a croct.plug() call in our app code because thats what the docs showed.
Now depending on load order I get either "Not plugged in" when my tracking code runs, or "Conflicting app ID" in the console. Sometimes both on teh same page load which is extra confusing. What am I doing wrong here?
1 answer
Both errors are pointing at the same root cause: you have two installs racing each other.
- "Not plugged in" means an SDK method (your tracking call) ran before croct.plug() had been called on that page load.
- "Conflicting app ID" means plug got called more than once with different app IDs, which is what happens when the old script tag and your new code each plug with their own ID.
The fix is one single plug call per page. Pick one install and delete the other: either keep the script tag in the layout and remove your croct.plug() from the app code, or (better if you are building on it) remove the script tag and keep the code path. Then make sure any tracking or evaluation calls run after plug, which they will once there is only one entry point.
Removed the old script tag and both errors are gone!! Thank you, I owe you one.