# Twitter Native Embed **URL:** https://meta.discourse.org/t/twitter-native-embed/261792 **Category:** Theme component **Created:** [April 15, 2023, 12:35pm UTC](https://meta.discourse.org/t/twitter-native-embed/261792 "2023-04-15T12:35:49Z") **Posts on this page:** 1 **Showing post:** 13
### Author: ![agemo](https://avatars.discourse-cdn.com/v4/letter/a/ac91a4/32.png) [@agemo](https://meta.discourse.org/u/agemo) #### Post date: [May 26, 2023, 6:07pm UTC](https://meta.discourse.org/t/twitter-native-embed/261792/13 "2023-05-26T18:07:56Z")
This is important and just discovered, by putting 2 and 2 together - if you had not CSP enabled before and you use say Google Adsense, you will nuke you ads turning on CSP if using encryption (DM’s) to get the twitter component to work as there is a potential conflict! I would like to be proven wrong with a super solution or _“you did it wrong”_ > [@Blank/Empty ads on Discourse Adsense Adplugin](https://meta.discourse.org/t/blank-empty-ads-on-discourse-adsense-adplugin/253100/12): > > Ah ha… that’s why adsense ads disappeared, it was the recently enabled CSP to allow the twitter component work! Trying the above ‘unsafe-inline’ can not be used when encryption is enabled for DM’s, now here we have a of web of unintended consequences if I ever saw one… thinking --- _[View the full topic](https://meta.discourse.org/t/twitter-native-embed/261792)._