{"_id":"585306492ebe5c0f00c6165c","user":"5668fa9755e4b32100935d41","project":"5668fab608f90021008e882f","version":{"_id":"5668fab608f90021008e8832","__v":19,"project":"5668fab608f90021008e882f","createdAt":"2015-12-10T04:08:22.769Z","releaseDate":"2015-12-10T04:08:22.769Z","categories":["5668fab708f90021008e8833","569740f124490c3700170a64","569742b58560a60d00e2c25d","569742bd0b09a41900b2446c","569742cd69393517000c82b3","569742f459a6692d003fad8f","569743020b09a41900b2446d","5697430b69393517000c82b5","56a17776470ae00d00c30642","56a2c48a831e2a0d0069b1ad","56b535757bccae0d00e9a1cd","56e1ff6aa49fdc0e005746b5","57e1c88115bf6522002a5e4e","57fa65275ba65a17008b988f","57fbeea34002550e004c032e","58474584889b6c2d00fb86e9","58475dcc64157f0f002f1907","587e7b5158666c2700965d4e","58a349fc30852819007ba083"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.18.0","version":"1.18"},"__v":0,"category":{"_id":"5697430b69393517000c82b5","version":"5668fab608f90021008e8832","__v":3,"pages":["56975a3d59a6692d003fadae","56a2c3dff4f3410d008a84dc","56d88ca37a04df0b00ddf1c7"],"project":"5668fab608f90021008e882f","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-01-14T06:41:15.588Z","from_sync":false,"order":10,"slug":"faq-troubleshooting","title":"FAQ / Troubleshooting"},"parentDoc":null,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-12-15T21:08:25.979Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":8,"body":"If you have multiple websites where you would like to run LiftIgniter, you have few different options.\n\nThe pros and cons listed on this page are primarily for JavaScript integrations. If you are using an API integration then you control the data flow much more and can choose whatever works well given the internals of your system.\n\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Create each website as a separate organization in our system (recommended)\"\n}\n[/block]\nIf you have a handful (less than 10) of fairly distinctive websites, we recommend using separate organizations (each with its own JavaScript) key for each of your websites.\n\nThis solution makes it easier to track user behavior separately for each website and makes tracking, reporting, and billing clearer. In particular, you will see data reported separately for each organization, so you can easily track the top items or top coviewed items within a website without having the data mixed up with other websites.\n\nWhen looking at the [Analytics Panel](doc:analytics-panel) or other parts of the LiftIgniter Lab, your team members can toggle displays between the organizations using a toggler on the top left.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Put all websites under a single organization\"\n}\n[/block]\nThis solution makes more sense if you have a single platform on which all the websites are hosted, and even more so if they are all subdomains of the same domain. An example would be a blogging or wiki platform with blog or wiki addresses as subdomains of your main domain.\n\nIn this case, if you want to restrict recommendations on an item to other items within the same website, you will need to set up a rule with us for [recommending from the same category](doc:recommend-specific-category-of-items).\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Cross-site recommendations\"\n}\n[/block]\nIf you are interested in recommending content across different websites, you should look up our documentation on [Cross-site recommendation](doc:cross-site-recommendation).","excerpt":"","slug":"multiple-websites-and-organizations","type":"basic","title":"Multiple websites and organizations"}

Multiple websites and organizations


If you have multiple websites where you would like to run LiftIgniter, you have few different options. The pros and cons listed on this page are primarily for JavaScript integrations. If you are using an API integration then you control the data flow much more and can choose whatever works well given the internals of your system. [block:api-header] { "type": "basic", "title": "Create each website as a separate organization in our system (recommended)" } [/block] If you have a handful (less than 10) of fairly distinctive websites, we recommend using separate organizations (each with its own JavaScript) key for each of your websites. This solution makes it easier to track user behavior separately for each website and makes tracking, reporting, and billing clearer. In particular, you will see data reported separately for each organization, so you can easily track the top items or top coviewed items within a website without having the data mixed up with other websites. When looking at the [Analytics Panel](doc:analytics-panel) or other parts of the LiftIgniter Lab, your team members can toggle displays between the organizations using a toggler on the top left. [block:api-header] { "type": "basic", "title": "Put all websites under a single organization" } [/block] This solution makes more sense if you have a single platform on which all the websites are hosted, and even more so if they are all subdomains of the same domain. An example would be a blogging or wiki platform with blog or wiki addresses as subdomains of your main domain. In this case, if you want to restrict recommendations on an item to other items within the same website, you will need to set up a rule with us for [recommending from the same category](doc:recommend-specific-category-of-items). [block:api-header] { "type": "basic", "title": "Cross-site recommendations" } [/block] If you are interested in recommending content across different websites, you should look up our documentation on [Cross-site recommendation](doc:cross-site-recommendation).