Title: Unexpected logout
Last modified: January 10, 2018

---

# Unexpected logout

 *  Resolved [Sailook](https://wordpress.org/support/users/sailook/)
 * (@sailook)
 * [8 years, 7 months ago](https://wordpress.org/support/topic/unexpected-logout/)
 * Hey,
    I just wanted to set up a retargeting pixel and saw the plugin automatically
   logged out, so I needed to re-authorize it in my WP dashboard. After that, I 
   saw my custom audiences were/are smaller than ever, even despite I had the basic
   pixel code installed on one of my pages. How can I fix that?
 * I was running a paid campaign to run retargeting ones after that and it looks
   like your plugin messed up my plans and waste my $ & efforts.
 * Does it work with other plugins like that? If it has bugs like that I’d rather
   to have more installed to backup my data.
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Funexpected-logout%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 8 replies - 1 through 8 (of 8 total)

 *  Plugin Author [Antonino Scarfì](https://wordpress.org/support/users/antoscarface/)
 * (@antoscarface)
 * [8 years, 7 months ago](https://wordpress.org/support/topic/unexpected-logout/#post-9852152)
 * Hi,
 * after a logout, anything shouldn’t be lost or changed, neither in website nor
   especially in your facebook account. So, after a new login, everything should
   continue to work as before to log out.
 * Regarding the size of custom audience, this indicator is not available anymore
   according to recent changes of Facebook Principles, more info here: [https://wordpress.org/support/topic/not-available-website-audiences/#post-9818007](https://wordpress.org/support/topic/not-available-website-audiences/#post-9818007)
 * So, I guess everything is working on your end and anything is wasted.
    You could
   check on your Facebook account: no worries if the custom audiences are there 
   and your campaigns are running correctly. 🙂
 *  Thread Starter [Sailook](https://wordpress.org/support/users/sailook/)
 * (@sailook)
 * [8 years, 7 months ago](https://wordpress.org/support/topic/unexpected-logout/#post-9852953)
 * Hey,
 * That’s pretty good news.
 * Just for the confirmation, so do the audience data are collected even during 
   the log-out time? I didn’t spot when it logged out.
 * I got scared because when I was choosing the custom audiences for my ads I saw
   the “20<” audience sizes inside of the FB ad manager.
 *  Plugin Author [Antonino Scarfì](https://wordpress.org/support/users/antoscarface/)
 * (@antoscarface)
 * [8 years, 7 months ago](https://wordpress.org/support/topic/unexpected-logout/#post-9855280)
 * Hi,
 * yes, you are correct. The audience data are collecting even log-out and even 
   if you aren’t able to see anymore the size of it.
 * Moreover, the plugin doesn’t take any action on log-out and also doesn’t (and**
   can’t** especially) do **nothing** when there isn’t connection to Facebook API.
   So, don’t worry! 🙂
 * If you confirm that everything is right now, I’d mark this topic as resolved.
   
   Thank you.
 *  Thread Starter [Sailook](https://wordpress.org/support/users/sailook/)
 * (@sailook)
 * [8 years, 7 months ago](https://wordpress.org/support/topic/unexpected-logout/#post-9855318)
 * Hey,
 * Cool, thank you 🙂
 * One more thing: on my another website I noticed I’m not able to create custom
   audiences inside the plugin and the current audiences are kind of blurred (screenshot:
   [https://i.gyazo.com/ed53e6a3d137fcd78885668284b832ec.png](https://i.gyazo.com/ed53e6a3d137fcd78885668284b832ec.png)).
   What does it mean?
 * Frankly, I don’t mind this state of things because the next audiences I’m gonna
   create in the FB ads manager, but I want to make sure my pixel is working correctly
   and everything’s fine.
 * I’m looking forward to hearing from you 😉
 *  Plugin Author [Antonino Scarfì](https://wordpress.org/support/users/antoscarface/)
 * (@antoscarface)
 * [8 years, 6 months ago](https://wordpress.org/support/topic/unexpected-logout/#post-9896401)
 * Hi,
 * very sorry to miss this reply, I”m seeing your response only now. Sorry for that.
 * About your request, you just check the Pixel Helper extension: if you see that
   the pixels are tracked properly, you shouldn’t have any problem 🙂
 *  Thread Starter [Sailook](https://wordpress.org/support/users/sailook/)
 * (@sailook)
 * [8 years, 6 months ago](https://wordpress.org/support/topic/unexpected-logout/#post-9899699)
 * Hey,
 * It looks ok now 😉 Btw what extension are talking about?
 *  Plugin Author [Antonino Scarfì](https://wordpress.org/support/users/antoscarface/)
 * (@antoscarface)
 * [8 years, 6 months ago](https://wordpress.org/support/topic/unexpected-logout/#post-9905013)
 * Hi,
 * I’m talking about the [Pixel Helper Chrome Extension](https://developers.facebook.com/docs/facebook-pixel/pixel-helper),
   it’s a very useful tool (from the official team of Facebook) to check the pixels
   fired from your website.
 *  Thread Starter [Sailook](https://wordpress.org/support/users/sailook/)
 * (@sailook)
 * [8 years, 6 months ago](https://wordpress.org/support/topic/unexpected-logout/#post-9906093)
 * Oh, ok – thx : )

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘Unexpected logout’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/pixel-caffeine_e2ce0c.svg)
 * [Pixel Caffeine](https://wordpress.org/plugins/pixel-caffeine/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/pixel-caffeine/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/pixel-caffeine/)
 * [Active Topics](https://wordpress.org/support/plugin/pixel-caffeine/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/pixel-caffeine/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/pixel-caffeine/reviews/)

 * 8 replies
 * 2 participants
 * Last reply from: [Sailook](https://wordpress.org/support/users/sailook/)
 * Last activity: [8 years, 6 months ago](https://wordpress.org/support/topic/unexpected-logout/#post-9906093)
 * Status: resolved