From 01eba5020554c1ca6b5be654b5da09de40af740f Mon Sep 17 00:00:00 2001
From: 7-liberal-arts <tthorner@infotinuum.com>
Date: Wed, 28 Oct 2020 14:26:38 -0400
Subject: [PATCH] Update common-user-flows-in-web-advertising.md

Is it worth revising "LinkedIn app" to "Facebook app" within the In-App-Browser => In-App-Browser section to maintain consistency between 1st party example and 3rd party example?
---
 common-user-flows-in-web-advertising.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/common-user-flows-in-web-advertising.md b/common-user-flows-in-web-advertising.md
index 732b65b..3c15397 100644
--- a/common-user-flows-in-web-advertising.md
+++ b/common-user-flows-in-web-advertising.md
@@ -33,7 +33,7 @@ _<example: ad shown on washingtonpost.com, served by Google’s ad network, dire
 ### 1st party:
 Ad is shown on a first-party website rendered within an in-app-browser within a native mobile app (i.e. App is just a wrapper around a webview). Clicking the ad opens another website in the same in-app-browser. 
 
-_<example: ad shown on LinkedIn app directing to adidas.com>_
+_<example: ad shown on Facebook app directing to adidas.com>_
 
 **Conversion attribution:** There are a few options.
 Use 3rd party cookies (or 1st party cookies with link decoration) that are scoped just to the in-app-browser.