{"id":226,"count":0,"description":"","link":"https:\/\/tenjin.com\/vi\/glossary\/install\/","name":"C\u00e0i \u0111\u1eb7t","slug":"install","taxonomy":"glossaries","parent":0,"meta":{"status":["1","1"],"order":["0","0"],"glossary_term_description":["
\r\n\r\nDefinition:<\/b>\r\n\r\nAn install in mobile marketing is recorded when a user opens an app for the first time after downloading it. Mobile app install attribution connects that install to the campaign, channel, or ad that drove it, which gives marketers the data they need to measure performance and optimize spend. Attribution relies on an app install attribution window, which defines how long after an ad interaction an install can be credited to that source.<\/span>\r\n\r\n<\/div>\r\n\r\n

What is an Install?<\/h2>\r\n\r\n\r\n\r\n\r\nAn <\/span>install<\/b> happens when a user downloads and opens a mobile app for the first time. In mobile marketing, it's one of the most fundamental events you can track. It\u2019s also one of the most important signals for measuring whether your campaigns are working.<\/span>\r\n\r\nBut an install isn't just a download count. When paired with <\/span>app install attribution<\/b>, it becomes a data point that tells you <\/span>where<\/span><\/i> that user came from, <\/span>which<\/span><\/i> campaign or channel drove the action, and whether that source is worth investing in further.<\/span>\r\n

What Counts as an Install?<\/span><\/h2>\r\nIn most mobile measurement frameworks, an install is recorded when a user launches an app for the first time after downloading it. This first open triggers an attribution event that connects the install to a source: a paid ad, an organic search, a social campaign, or a referral link.<\/span>\r\n\r\nThis is where <\/span>attributing mobile app installs<\/b> gets nuanced. Not every download becomes a recorded install. If a user downloads an app but never opens it, the install event is never fired. This distinction matters when you're comparing store download numbers against attributed installs in your dashboard.<\/span>\r\n

How Mobile App Install Attribution Works<\/span><\/h2>\r\nMobile app install attribution<\/b> is the process of identifying which marketing source is responsible for an app install. When a user taps an ad and then installs your app, attribution connects those two events. This then assigns credit to the right campaign, network, or channel.<\/span>\r\n\r\nHere's a simplified version of how it works:<\/span>\r\n<\/span>\r\n
    \r\n \t
  1. A user sees or clicks an ad<\/span><\/li>\r\n \t
  2. They download and open the app for the first time<\/span><\/li>\r\n \t
  3. The attribution provider matches the install to the original touchpoint<\/span><\/li>\r\n \t
  4. That data is sent back to your dashboard and your ad network<\/span><\/li>\r\n<\/ol>\r\nThe matching process relies on signals like click timestamps, device identifiers, and probabilistic modeling when deterministic data isn't available. This is where a reliable MMP (Mobile Measurement Partner) like Tenjin makes the difference. It ensures your installs are matched accurately, not just approximately.<\/span>\r\n

    App Install Attribution Window<\/strong><\/h2>\r\nThe <\/span>app install attribution window<\/b> is the period of time during which an install can be credited to a specific ad interaction. If a user clicks an ad and installs the app within that window, the install is attributed to that click. If they install after the window closes, it may be attributed to a different source or marked as organic.<\/span>\r\n\r\nCommon attribution windows include:<\/span>\r\n