{"metadata":{"image":[],"title":"","description":""},"api":{"url":"","auth":"required","settings":"","results":{"codes":[]},"params":[]},"next":{"description":"","pages":[]},"title":"Model customizations","type":"basic","slug":"model-customizations","excerpt":"Edit your model to fit your sales cycle or company type","body":"Once you've gotten comfortable with the model types in Attribution you can begin to start making customizations to your model to suit your company's needs. The primary model customization you can make is based around how you choose to handle direct traffic. There are four options to choose from, below we will go into each in greater detail. \n[block:api-header]\n{\n  \"title\": \"Include All Traffic: all traffic is included in your model\"\n}\n[/block]\nInclude all traffic is exactly as it sounds, with this setting you would include all traffic in your model not disregard any visits. What this means is that when you select a linear model for example your paid traffic would split credit with direct traffic. \n\nTherefore if a visitor visited on Monday from a Facebook ad, then Tuesday directly, and converted on Wednesday, Facebook & direct traffic would both get 50% credit for that conversion. \n\nThis is typically best for eCommerce companies or companies that may have disconnected transactions. \n\nIn the image below we can consider the blue 'look forward' window as the data being captured. With all traffic every touch point is considered and given credit. \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/a15fe19-Lookforward-_All_traffic_included_-_Time_Decay_1.jpg\",\n        \"Lookforward- All traffic included - Time Decay (1).jpg\",\n        582,\n        377,\n        \"#333\"\n      ]\n    }\n  ]\n}\n[/block]\n\n[block:api-header]\n{\n  \"title\": \"Include all direct traffic until a cut off event\"\n}\n[/block]\nThis modification adds a slight variation to the 'all traffic included' setting where it will include all direct traffic until a specific cutoff event.  This customization is often used by SaaS companies who only want to attribute credit to their ad channels before the customer has signed up or subscribed. SaaS companies would do this because the direct traffic may dilute the credit for their advertising channels after the visitor has subscribed since the visitor will rack up direct traffic as they visit the site to use their tool. \n\n\n[block:api-header]\n{\n  \"title\": \"Exclude all direct traffic: remove direct traffic from your model\"\n}\n[/block]\nWith this customization Attribution app will never consider direct traffic. This is beneficial for companies that have customers visit their site regularly to use a tool or sign in etc. \n[block:api-header]\n{\n  \"title\": \"Exclude all direct traffic after a cut off event\"\n}\n[/block]\nWith this customization Attribution app will stop attributing credit for any channel either direct or indirect after a specific cutoff event. This is best for companies that have a subscription service with a free trial where after the customer is sold you don't want to consider attribution for them. \n\nIf you have any questions on model customizations please contact help:::at:::attributionapp.com","updates":[],"order":1,"isReference":false,"hidden":false,"sync_unique":"","link_url":"","link_external":false,"_id":"6012a15e707fbf00184167e0","createdAt":"2021-01-28T11:34:54.465Z","user":"560c92f2ac2859170013faa3","category":{"sync":{"isSync":false,"url":""},"pages":[],"title":"Model types","slug":"attribution-model-examples","order":6,"from_sync":false,"reference":false,"_id":"57c722ecdf19130e001fba5d","project":"560c93ad7e9b9d0d00ca81a2","version":"560c93ae7e9b9d0d00ca81a5","createdAt":"2016-08-31T18:33:16.326Z","__v":1},"version":{"version":"1.0","version_clean":"1.0.0","codename":"","is_stable":true,"is_beta":false,"is_hidden":false,"is_deprecated":false,"categories":["560c93af7e9b9d0d00ca81a6","560c9d9399bb5a0d0044f220","560d76d899bb5a0d0044f307","560d76ee1ec45619006069ed","560d86e099bb5a0d0044f32e","560dba80373c0e0d0024ff3b","57c722ecdf19130e001fba5d","57c743d1b6f94a2200659903","58995ec083f743190077bbe2","5fabfb070e9b0600424707dd","60004359deee820012dc1efc","600060c72dcd9d002fa13656","6001ac08c104fe002b933b7c","6009604d81b288001417df30","60097b7be8ec1e00334419f6","600aa98de28fae003a33108a","600aa9ee7d3e350018e7d6e4","601176819ca8c90011cfe6ac","606eef795bb7ed00790e9e68"],"_id":"560c93ae7e9b9d0d00ca81a5","project":"560c93ad7e9b9d0d00ca81a2","createdAt":"2015-10-01T02:00:14.709Z","releaseDate":"2015-10-01T02:00:14.709Z","__v":19},"project":"560c93ad7e9b9d0d00ca81a2","__v":0,"parentDoc":null}

Model customizations

Edit your model to fit your sales cycle or company type

Once you've gotten comfortable with the model types in Attribution you can begin to start making customizations to your model to suit your company's needs. The primary model customization you can make is based around how you choose to handle direct traffic. There are four options to choose from, below we will go into each in greater detail. [block:api-header] { "title": "Include All Traffic: all traffic is included in your model" } [/block] Include all traffic is exactly as it sounds, with this setting you would include all traffic in your model not disregard any visits. What this means is that when you select a linear model for example your paid traffic would split credit with direct traffic. Therefore if a visitor visited on Monday from a Facebook ad, then Tuesday directly, and converted on Wednesday, Facebook & direct traffic would both get 50% credit for that conversion. This is typically best for eCommerce companies or companies that may have disconnected transactions. In the image below we can consider the blue 'look forward' window as the data being captured. With all traffic every touch point is considered and given credit. [block:image] { "images": [ { "image": [ "https://files.readme.io/a15fe19-Lookforward-_All_traffic_included_-_Time_Decay_1.jpg", "Lookforward- All traffic included - Time Decay (1).jpg", 582, 377, "#333" ] } ] } [/block] [block:api-header] { "title": "Include all direct traffic until a cut off event" } [/block] This modification adds a slight variation to the 'all traffic included' setting where it will include all direct traffic until a specific cutoff event. This customization is often used by SaaS companies who only want to attribute credit to their ad channels before the customer has signed up or subscribed. SaaS companies would do this because the direct traffic may dilute the credit for their advertising channels after the visitor has subscribed since the visitor will rack up direct traffic as they visit the site to use their tool. [block:api-header] { "title": "Exclude all direct traffic: remove direct traffic from your model" } [/block] With this customization Attribution app will never consider direct traffic. This is beneficial for companies that have customers visit their site regularly to use a tool or sign in etc. [block:api-header] { "title": "Exclude all direct traffic after a cut off event" } [/block] With this customization Attribution app will stop attributing credit for any channel either direct or indirect after a specific cutoff event. This is best for companies that have a subscription service with a free trial where after the customer is sold you don't want to consider attribution for them. If you have any questions on model customizations please contact [email protected]